This sounds weird. However, SQLite gets complete support for the web setup which should solve a lot of headaches. A new beta of v2 will be released this week, you could try again after this.

Also, I noticed the docs for v2 are quite outdated compared to v1.

I tried a docker install of v2 beta today and could not get it running with sqlite, but that might have been a config error on my part. I also tried v2 beta docker with mysql and got the containers up, no errors in the container logs, but couldn't reach the webserver in browser or curl - no port conflicts. Nothing in the logs about caddy running. Will take a closer look at the dockerfiles in the next few days and see if I can figure out why caddy didn't start.

I have not released the new version yet, so it might make sense to wait. Sorry.

No worries and no rush intended. I'll keep an eye out for it.

Beta 2 is out now with the new setup process.

Setup was successful in a non-docker sqlite using Beta 2. I could close this one and create a new issue for Beta 2 issues - let me know what you prefer. I ran into an import issue that I document below.

From CLI:

`In Connection.php line 829:

SQLSTATE[23000]: Integrity constraint violation: 19 NOT NULL constraint failed: links.visibility (Connection: sqlite, SQL: insert into "links" ("user_id", "url", "title", "description", "icon", "visibilit
y", "created_at", "updated_at") values (1, https://support.mozilla.org/products/firefox, Get Help, ?, link, ?, 2022-07-04 11:42:17, 2024-09-08 08:27:16))`

and

`In Connection.php line 587:

SQLSTATE[23000]: Integrity constraint violation: 19 NOT NULL constraint failed: links.visibility`

This same html file imports successfully in Linkace V1 Docker with MySQL. I believe it is the first link in the file. I will test with another backend on Beta 2 later.

Thanks, I will have a look at this in a separate ticket.