Configration, deployment and additional things

bhunter - 2 months ago

Hi all,

I'm new to pyrocms and after checking documentation I was not able to find the following answers: When I add my project files to repo, and change something from admin panel (for example some option or add a page or whatever) where is this stored? If other team member access my repo, can he run php artisan migrate or something to actually have the latest changes in his local env?

Regarding theme: I tried to install this: which requires Pyro Builder however links are dead?!? On the other hand I was able to find but when I run first command I get:

Problem 1 - Conclusion: don't install websemantics/builder-extension 1.1.3 - Conclusion: don't install websemantics/builder-extension 1.1.2 - Conclusion: don't install websemantics/builder-extension 1.1.1 - Conclusion: remove nikic/php-parser v3.0.5 - Installation request for websemantics/builder-extension ^1.1 -> satisfiable by websemantics/builder-extension[1.1.0, 1.1.1, 1.1.2, 1.1.3]. - Conclusion: don't install nikic/php-parser v3.0.5 - websemantics/builder-extension 1.1.0 requires nikic/php-parser ~2.0 -> satisfiable by nikic/php-parser[v2.0.0, v2.0.1, v2.1.0, v2.1.1]. - Can only install one of: nikic/php-parser[v2.0.0, v3.0.5]. - Can only install one of: nikic/php-parser[v2.0.1, v3.0.5]. - Can only install one of: nikic/php-parser[v2.1.0, v3.0.5]. - Can only install one of: nikic/php-parser[v2.1.1, v3.0.5]. - Installation request for nikic/php-parser (locked at v3.0.5) -> satisfiable by nikic/php-parser[v3.0.5]. Not sure how to proceed...

Any ideas?

Thank you.

edster - 2 months ago

I used the webstmantics builder yesterday.

Check to make sure your pyro env is up to date and it is in your composer.json file properly.

fryiee - 2 months ago

Re your first question, information changed in the admin panel will be saved in the database, so you'll need to either seed changes or have some sort of export / backup in place for your database.

ryanthompson - 2 months ago

@bhunter hi there!

So.. a lot of the configuration you see in settings and such can be set as .env variables and/or overridden by published config files. In the case of setting the values in .env file then it will actually lock the setting via the control panel so it cant be tampered with.

Regarding theming - I would recommend just using the included theme / addon generators. The builder setup has a small learning curve. Where as it is best to get to know the basics first.

^ That will get you up and running with a vanilla bootstrap theme in no time.

Hope this helps!