[scottnathMember]

Is it possible to set up a Pod and/or item in a file instead of the UI interface?

I don’t mean data into an existing pod, I mean the pod itself and its corresponding columns.

The reason I ask is in larger sites, where the site is in multiple environments (ie DEV, QA, STAGE, PROD, etc) we need the ability to move changes (such as a new column) from env to env without moving the database.

If this isn’t in 1.X, do you think it could be something in 2.0?

thank you,
Scott

[magi182Member]

Hey Scott, Check out the Pods Package Manager.

PHP

<a href="http://podscms.org/codex/package_manager/" rel="nofollow">http://podscms.org/codex/package_manager/</a>

1	<a href="http://podscms.org/codex/package_manager/" rel="nofollow">http://podscms.org/codex/package_manager/</a>

While it isn’t exactly a file, it does allow you to move the structure of a pod, helpers, templates, without moving the data.

[scottnathMember]

Thanks for that, but not what we’re looking for.

Essentially, what happens in a multi-environment setup is you make changes in DEV, the files get moved to QA for testing, then moved to STAGE to re-test in an exact copy of the PROD env, then changes are put into PROD.

The issue we run into with WordPress being so database-centric is that we can’t really make changes to the database by moving a database. And, it is very accident-prone to try and re-create our changes in the Admin interface (Will I remember all the steps I did before?) Therefore, we’re trying to figure out ways to have options/setups happen in files instead. That way, we just check them into the repository and check them out in the next environment.

I realize it’s a tall order, but necessary for our setups. The idea is similar to what this custom fields plugin does:

http://wordpress.org/extend/plugins/custom-metadata

thanks for the response,
Scott

[Author]

Posts