search

smrose / ActivistMirror

What kind of Activist are you? Answer a small set of questions to find out.
0 stars 0 forks source link

Presumably you'll move the new strings... #28

Closed publicsphere closed 2 weeks ago

publicsphere commented 2 weeks ago

When I get to the translate tool, I'll make changes to the ambeta tables. Then, presumably, you'll move the data to am tables.

This may be obvious but I thought I'd ask.

smrose commented 2 weeks ago

We have two versions of the application - the older "am" version, which uses the "amirror" database, and the in-development "ambeta" version, which uses the "ambeta" database. Each application has its own schema and set of strings. So moving the strings from "ambeta" to "amirror" isn't something that can be done. You should explain what you are hoping to achieve so I can understand why you propose that step and can formulate a plan to achieve the goal via a set of steps that would do it.

publicsphere commented 2 weeks ago

We are now testing on the ambeta version. So, if I make changes to strings via translate.php, won't the changes be made to the ambeta database? And, if that's the case, won't I have to go in and make all of same changes to the am database? (I.e. I certainly would need to keep track of them)

smrose commented 2 weeks ago

The ambeta version of the application uses the ambeta database so that version of the translate tool operates on the strings in the ambeta database . The legacy am version of the application uses the am database and its version of the translate tool operates on strings in the am database. The databases have different schemas, though the ambeta schema is based on the am schema. Strings in the ambeta database can't universally be copied to the am database because of schema differences. But - why would we want to? What goal would be be serving doing that?

The beta application currently has the URL https://labs.publicsphereproject.org/ambeta/ while the legacy application has the URL https://labs.publicsphereproject.org/am/

Eventually, we will promote the beta application and demote the legacy version. To do that, what needs to happen is that the URL of beta application changes s/ambeta/am/ - if we still like that URL - and the URL of the legacy application changes something like s/am/am-legacy/. Imagine the following sequence of shell commands:

% cd labs.publicsphereproject.org
% mv am am-legacy
% mv ambeta am

That's all that's needed to change the URLs. It's true that the database used by what's now the gold application is still called ambeta and of the legacy application still uses am. That could be fixed by renaming the databases and editing the two db.php files if it bothers us.