search

preaction / Statocles

Static website CMS
http://preaction.me/statocles
Other
84 stars 33 forks source link

Get the build working #583

Closed wbazant closed 4 years ago

wbazant commented 4 years ago

I think it worked anyway despite not being in the schema.

The util module is from v0, and I've only noticed the missing import after bin/statocles daemon no longer worked when I created an isolated development environment.

wbazant commented 4 years ago

Perl 5.14 binary disappeared, I assume it will come back. The rest is, I think, good now.

wbazant commented 4 years ago

Adding tags to schema is a bigger change, because Yancy's UI isn't ready for it yet. We would like to be able to edit the tags when viewing the pages at localhost:3000/yancy: add, save, remove, etc. but just adding them to the schema is not adequate.

I've force pushed that change away. Now this PR is meant to just include this:

Get build working

- removes Statocles::App::Perldoc: not v2 ready
- bring back v1's Statocles::Util because Statocles::App::Deploy needs it
- imports
- minor tests for tag pages and conf being present
preaction commented 4 years ago

Huh. Yeah, that only all worked because I've got the old Statocles installed while running the new Statocles's tests... Long-term, I'd like to get rid of the Path::Tiny dependency since Mojolicious has Mojo::File, and most of the things in Statocles::Util can go away (just dircopy and derp probably, since there will likely be future deprecations...).

Statocles::App::Perldoc is going to be replaced with Mojolicious::Plugin::PODViewer, which just needs some integration testing.

Adding simple array support to Yancy is definitely on the roadmap for that project, among other things. Simple arrays of non-container types would probably be an easier first step than full foreign key / object embedding support. Either way, yes, that's where that'll have to go.

So, this looks good, thanks!