mlposey / mutably Goto Github PK

The usage info just blasts you with information, and action flags (those that specify what anvil should do) use the same syntax as other flags like verbosity.

Clean up the front-end display first. Then look into cleaning up the blob of code in anvil.go.

The database structure in mutably will need to be changed, which involves normalizing the verbs table. That modification will require changing the *Verb.AddTo method.

Verbs will have their own table and so will templates. This structure may fix the duplicate key issue. At the very least, it is a better design.

The import arguments that are passed to anvil from the docker-compose file are ignored. I haven't looked into this for a few days, but I believe the issue was that CMD and ENTRYPOINT handle argument lists differently depending on if one uses shell or command syntax.

Should an external volume contain the .xml or should the dockerfile run wget and then decompress the dump?

The mock db doesn't match the new interface

This can likely be fixed by setting mutably as the root package, making the old root anvil become mutably/anvil and so on.

Steps to reproduce:

1. Acquire the latest pages-meta-current dump.
2. Run import on the dump using any valid database credentials.

Error output:
pq: duplicate key value violates unique constraint "templates_pkey"

This will likely involve some docker setup. The level of automation involved means it's probably a good idea to set up a CI tool (like Jenkins or GitLab) first.

The verb insertion procedure skips languages not found in the languages table. Implement dynamic additions.

Using TeeReader to send chunks of attributes to decoding goroutines/workers may help.