well, it seems that first steps of deploying a contentbox war file is quite frustrating. I’d have expected that if I get a web archive I just drop it to any container, let it unpack and run any kind of installer. Ouh, but what happens here is that after it’s unpacked and the app is requested I just get a
Even if I read readme.md I’m left alone as there a no hints for this kind of installation or configuration. There are no explanations how to continue. I think I need some idiot proofed tutorials what to do if I start with a simple bash. I did quite a lot a coldfusion development 25 years ago and thought I give it a chance. But documentation seems to be a big pain. 7 years old YT content can’t convice. Am I at the end immediately?
We have dropped support for war deployment since version 4.x. Due to trying to support the many underlying issues of a servelet container plus the many versions of lucee with their supported and unsported features, it just became a pain.
Especially dealing with datasources in a WAR environment and seeding the engine with the datasource, building the initial database, etc.
Therefore, that was dropped from us directly since version 4.
Now, with that said, you can build your own WAR archive YOUR way. ContentBox is now intsallable via a our contentbox-cli. Which then you can use to prep your database of choice. Once that’s build, you can then package it and send it to your serlvet of choice.
and I’m pretty sure my Postgres is running and I entered the right credentials, but it CLI complains about
Make sure your database (contentbox) has been created!
If this process fails, then your database credentials are not correct. Verify them and make sure they match the ones in the (.env) file we created.
You don't have to run the installer again if it fails. You can run the following commands to finish your installation:
- migrate install
- run-script contentbox:migrate
Please wait while we install your migrations table...
Storing cfmigrations information in box.json has been deprecated in v4 and will be removed in v5.
Please refer to the migration guide at https://github.com/commandbox-modules/commandbox-migrations to upgrade.
The format of the migrations configuration has changed in v4.
We will convert your configuration to the new format. This auto-conversion will be dropped in v5.
Please refer to the migration guide at https://github.com/commandbox-modules/commandbox-migrations to upgrade.
ERROR (6.0.0+00787)
No manager found named [contentbox]. Available managers are: default
and the “webinstaller” says: lucee.runtime.exp.CustomTypeException: Error building: AuthorService@contentbox -> ORM is not enabled .
I created a database “contentbox” by hand, which still feels strange as I define credentials and someone could image that an installer could do this job?!
I don’t think you have the latest migrations installed. Please do a uninstall commandbox-migrations --system and reinstall it install commandbox-migrations.
If you can’t get the CLI to install the database, then we can’t move to the web portions. You should have a .cfmigrations.json in the root.
Mmh, not sure why I should be out of date if I had a fresh installation and started with an update --system command?
But I did what you suggested. Still the result of my contentbox install-wizard is:
Make sure your database (contentbox) has been created!
If this process fails, then your database credentials are not correct. Verify them and make sure they match the ones in the (.env) file we created.
You don't have to run the installer again if it fails. You can run the following commands to finish your installation:
- migrate install
- run-script contentbox:migrate
...
ERROR (6.0.0+00787)
No manager found named [contentbox]. Available managers are: default
I double check the .env and find valid credentials (third check is to use psql manually):
Anyone with an idea?
To check my assumption I monitor with tcpdump any connections to my postgres at port 5432.
But nothing arrives
A restart of the box command and the start of the “contentbox install-wizard” gave me this time (at the end):
Do you wish to continue? [y/n] : y
Starting to install ContentBox...
× | Installing package [forgebox:contentbox-installer@y]
|-------------------------------------------------------------------
| Verifying package 'contentbox-installer@y' in forgebox, please wait...
| Error getting ForgeBox entry [contentbox-installer@y] The entry slug sent is invalid or does not e
| xis
|-------------------------------------------------------------------
ERROR (6.0.0+00787)
Error getting ForgeBox entry [contentbox-installer@y]
The entry slug sent is invalid or does not exist
To apply again the previos mentionend uninstall/install of suspicious components I did an:
Hi @Rainer another issue reported some issues with the ContentBox CLI. So I would suggest that you update it as we just applied tons of fixes for the cli.
box update contentbox-cli --force
Remove all databases, files and do another install
Hi @lmajano, after your suggestions the error message changed to:
Make sure your database (contentbox) has been created!
If this process fails, then your database credentials are not correct. Verify them and make sure they match the ones in the (.env) file we created.
You don't have to run the installer again if it fails. You can run the following commands to finish your installation:
- migrate install
- run-script contentbox:migrate
Please wait while we install your migrations table...
ERROR (6.0.0+00787)
Authentication type 10 is not supported. Ensure that the 'pg_hba.conf' file contains the IP address or subnet of the client and that the client uses an authentication scheme that is supported by the driver.
would recommand to change to MD5 hashes. My try didn’t succeed. Finally it seems to be a JDBC → PostgreSQL 14 problem. This explains why all cli tests with psql (and my used credentials) run without any issues where on the other hand JDBC fails.
