unzip serge-master.zip unlink serge-master.zip cd serge-master
serge pull --initialize.)
serge and I got a error like this.
Initializing the database... Exception occurred while processing job 'my_project.job': Can't open schema file /usr/lib/serge-master/bin/../lib/Serge/pg_schema.sql: No such file or directory
Then I looked the github repo, and I didn't see pg_schema.sql but I can see schemas for mysql and sqlite3.
Is there any way to tackle it.
Thanks in advance :)
@JAINKJOHNSON_twitter potentially Serge can work with Postgress (as with any other RDBMS that has a DBI driver); practically, it was tested and currently supports only MySQL and SQLite. When you use any driver in the database connection string, and the database doesn't exist, Serge tries to locate the
lib/Serge/xx_schema.sql file where
xx is the driver name. For postgress that would be
pg. And Serge doesn't ship with such a file (it only has
sqlite_schema.sql). This shema file is a set of SQL statements that one needs to run on a blank database to initialize all the tables and indices. If you want to use Postgres, you can take
mysql_schema.sqlfile as a starting point and create
pg_schema.sql from it, possibly altering for Postgres-specific syntax. If that works, feel free to do a PR with the schema file.
Having said that, I typically encourage everybody to start with an SQLite database. It's fast, simple, and usually more than enough for practical purposes. The database is a single file that you can easily backup and restore.
@locpeople even if XTM has an API, it won't give you a proper continuous localization workflow (because of the jobs mentioned above) and ultimately won't allow you to approach proper translation quality (all jobs are translated out of global context). So I'd strongly recommend finding some solution that is not job-based.
Answering your questions on TM, Serge accumulates translations in its own database, but there's no 'management' part there. You will simply have translations stored in Serge in addition to whatever CAT frontend you use stores.
@elrasskazenok_twitter I think it could be due to evernote/serge#85
For now, since this is the only test failing, you can try installing this with the
--force flag. Should work fine.
COPYcommand. Will probably move that back. Your solution is correct. My command was
docker build --no-cache -t serge -f docker/Dockerfile ., ran from the root Serge folder. (I kept no intermediate cache and explicitly tagged the image as