Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Migrate from Mojolicious to Cro #2910

Closed
JJ opened this issue Jul 19, 2019 · 1 comment
Closed

Migrate from Mojolicious to Cro #2910

JJ opened this issue Jul 19, 2019 · 1 comment
Assignees
@Altai-man
Labels
wishlist "nice to have" issues; might require a lot of work or a big change or be low priority

Comments

@JJ
Copy link
Contributor

JJ commented Jul 19, 2019

The problem

In general, the doc site can be deployed as a set of static pages. Far as I can tell, what the Mojolocious app does is to check if some asset for generating CSS has changed and recompile it.

Suggestions

I'm not sure we even need to do that. As a matter of fact, if we use a deploy script as indicated in #2909 we might include it there so that it's run every time it's deployed. But it would be interesting to explore the possibility anyway.
@JJ JJ added build wishlist "nice to have" issues; might require a lot of work or a big change or be low priority labels Jul 19, 2019
@Altai-man Altai-man self-assigned this Nov 7, 2020
@Altai-man Altai-man mentioned this issue Mar 13, 2021
Closed
@coke
Copy link
Collaborator

coke commented Feb 3, 2023

Can already run the new doc-website in Cro (even if the prod site there is static to start).

@coke coke closed this as completed Feb 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Altai-man Altai-man

Labels
wishlist "nice to have" issues; might require a lot of work or a big change or be low priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@JJ @coke @Altai-man and others