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.

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

Create A Nice Web Form For config.php & Basic Style Generation #4

Open
Cheeseness opened this Issue May 13, 2012 · 2 comments

Comments

Projects
None yet
2 participants
@Cheeseness
Owner

Cheeseness commented May 13, 2012

It would be nice to have a web form to tweak/adjust the settings in config.php and maybe also some style generation that responds to things like whether or not there's a twitter feed.

@ghost ghost assigned Cheeseness May 13, 2012

@marcusmoller

This comment has been minimized.

Show comment
Hide comment
@marcusmoller

marcusmoller Dec 22, 2012

Contributor

It would be possible to create a config in similar way as to how Wordpress does it:
https://github.com/WordPress/WordPress/blob/master/wp-admin/setup-config.php

I could pretty easily and fast wrap up some code which just uses fopen/fwrite to create a new config.php, but I am unaware if there might be some implications with this method.

Contributor

marcusmoller commented Dec 22, 2012

It would be possible to create a config in similar way as to how Wordpress does it:
https://github.com/WordPress/WordPress/blob/master/wp-admin/setup-config.php

I could pretty easily and fast wrap up some code which just uses fopen/fwrite to create a new config.php, but I am unaware if there might be some implications with this method.

@Cheeseness

This comment has been minimized.

Show comment
Hide comment
@Cheeseness

Cheeseness Dec 22, 2012

Owner

That's pretty much what I was going to do, but I've since created a separate (currently empty) project to contain this sort of stuff, so as to keep the amount of bloat in Para CMS itself to a minimum.

https://github.com/Cheeseness/para-tools

Owner

Cheeseness commented Dec 22, 2012

That's pretty much what I was going to do, but I've since created a separate (currently empty) project to contain this sort of stuff, so as to keep the amount of bloat in Para CMS itself to a minimum.

https://github.com/Cheeseness/para-tools

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment