New Self-hosted Version Progress & issues #5069
Comments
EYHN
added
state:in-progress
type:epic
|
🏆 a self-host tutorial on synology would be golden 🙌 |
|
@omarcostahamido I think there is endless potential for integration into other managed systems.
|
|
Yes synology DSM, that's what I meant. I'm happy to help with it! |
|
I have a synology and I prefer have a docker compose setup |
|
Waiting for official Docker image (ARM64). This is required for any server-side projects nowadays :) |
|
Looks like the docker build for selfhost support got merged recently. Excited to try this! |
The new version drop few hours ago can be run on ARM64 using a raspberry pi 4 😄 |
|
The new version for self hosted is running but i have this message : My server not gonna save my note ? or it's a UI bug ? |
|
I tried to run this docker-compose on my server too, but i faced with several issues:
I can provide any help that you need with self-hosted version, even write instructions on how to run affine on cloud-ocean droplet or drop docker image on TrueNas Scale. |
|
@Exitialis Thank you for sharing your experience and the workarounds that you found!
I guess that's why #2646 is open? |
The server is not gonna save you note unless the cloud is enabled. All data will be saved in the browser's local storage. |
|
I tried running the self-host docker-compose myself but whatever should run on port 5555 isn't starting |
|
|
I see, thank you @Brooooooklyn! Then I have some other issue, if I go to http://123.123.123.123:3010 I just see this: {"compatibility":"0.12.0","message":"AFFiNE 0.12.0 Server","flavor":{"type":"allinone","main":true,"sync":true,"selfhosted":false}}I can see the logs saying this:
But If browse to https://affine.example.com I get a cloudflare timeout. What are the steps to troubleshoot here? |
|
@benjick I had the same issue, which stemmed from me using the docker-compose.yaml from the canary-branch instead of 0.12.0. On canary SERVER_FLAVOR is not set, compared to 0.12.0 where the following is added in the docker-compose file:
Although my service now comes up as expected and my redis and graph db are both up and running and configured, I still get the prompt, that my data is only stored in the browser instead of in the database: |
|
I see the same issue as above, when I try to sign in - the frontend says "GraphQL empty body" And the docker log: |
@fourdim What is the GraphDB used for then? My understanding was, that we'd be able to save the data to the locally run graph db service. |
|
As an addendum, I get the same error listed above after trying out the :stable version too. |
|
Sorry, our self-hosted version is not yet ready, as it seems that the configuration module is not working properly. Since it is already outside of working hours in our engineers' time zone, I believe we will resolve this issue tomorrow. |
Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/app/scripts/register.js' imported from /app/
> > FYI, just noticed this after the announcement today. There is a docs.affine.pro page that has a self-host tutorial now: https://docs.affine.pro/docs/self-host-affine-
>
> I get node errors using the provided unmodified self-hosted compose.yaml
>
> ```
> affine_selfhosted | node:internal/errors:496
> affine_selfhosted | ErrorCaptureStackTrace(err);
> affine_selfhosted | ^
> affine_selfhosted |
> affine_selfhosted | Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/app/scripts/register.js' imported from /app/
> affine_selfhosted | at new NodeError (node:internal/errors:405:5)
> affine_selfhosted | at finalizeResolution (node:internal/modules/esm/resolve:327:11)
> affine_selfhosted | at moduleResolve (node:internal/modules/esm/resolve:980:10)
> affine_selfhosted | at defaultResolve (node:internal/modules/esm/resolve:1193:11)
> affine_selfhosted | at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:403:12)
> affine_selfhosted | at ModuleLoader.resolve (node:internal/modules/esm/loader:372:25)
> affine_selfhosted | at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:249:38)
> affine_selfhosted | at ModuleLoader.import (node:internal/modules/esm/loader:335:34)
> affine_selfhosted | at node:internal/process/esm_loader:26:84
> affine_selfhosted | at node:internal/per_context/primordials:544:39 {
> affine_selfhosted | url: 'file:///app/scripts/register.js',
> affine_selfhosted | code: 'ERR_MODULE_NOT_FOUND'
> affine_selfhosted | }
> affine_selfhosted |
> affine_selfhosted | Node.js v18.19.1
>
|
i can confirm the |
The PR #5920 was recently merged. The documentation has been updated, but obviously, the new version of stable tag hasn't been published yet. You just need to restore the environment. - - NODE_OPTIONS="--import=./scripts/register.js"
+ - NODE_OPTIONS="--es-module-specifier-resolution=node" |
|
Thanks to the tip from the person above, I managed to get Affine running locally. However, please don't have too high expectations as it is still a fair way off from replacing Notion at this point.
|
|
@xuqingkuang thanks for the reply, I managed to get it up'n'running but there's a bit of inconsistency I'm missing. by default, it spins up the graphql server on port :3010. using comment above #5069 (comment) it drops the graphql server and spins up the web UI on the same port but when I try to login is looking for :3010/graphql that's not available anymore. in theory i can spin up 2 instances and route the requests to /graphql to server instance using traefik for example, i'll try it later on and see if this a solution 🤞 |
|
@peterbuga looks like graphql cloud be on secondary port... or two containers? But honestly it sounds like classic case of two services trying claiming the same port. Fore somebody with knowledge of the architecture should not be a very hard fix. |
|
@PovilasID I did some testing, using 2 containers and routing the thanks for all the hard work! i'll keep an eye on the project |
|
For me, the app under port 3010 responds with the following at {"compatibility":"0.12.0","message":"AFFiNE 0.12.0 Server","flavor":{"type":"allinone","main":true,"sync":true,"selfhosted":false}}The |
|
@PhilippMolitor you need to add: |
|
|
|
we are recommending you start the selfhost server with docker image distribution(canary/beta/stable) the same as branch(canary/beta/stable) where your compose file located at. there always some difference in between the compose file and docker image for different branches. for example, if you are in affine repo at we've already updated the docs to tell cloning with stable branch: git clone https://github.com/toeverything/AFFiNE.git --branch stableBTW, don't forget to pull the latest images |
|
Hello, with the last update i can't login to the "connect to AFFINE Cloud" form, i'm redirect every time to |
|
|
|
I encounter the following errors when using docker compose to do the self-hosting deployment. "Error: Command failed: yarn predeploy the branch I clone is 'stable' and the image is also tagged 'stable' |
|
image loading fail 
|
|
I was able to get it running using the provided instructions. Is it limited to just the admin user for now? Can I open it to registration for other users, and share pages between users? |
|
@endquote |
|
@acranglesim the env setting My Affine server logs show the following: Maybe NextAuth doesn't pick up the correct url from the affine server env config? |
|
@PhilippMolitor same issue with login via email-address. |
|
@EYHN consider reopening and help users with their issue? |
|
@PhilippMolitor @Kerber0ss |
|
@markoott |
Thanks @doldremus. I set up these env vars and tried to invite someone else to a workspace. I got this error: Here are my settings: I've had issues with this no-password thing in other apps, I wonder if that's the issue here. I tried entering an email into the registration form, but I did not see the same error in the log. Maybe it only happens once. I could make this a new issue somewhere else since this thread is getting mixed. |
|
Please open a new issue if you need help |
|
For those who have problems with the login form, I posted my solution here: #6007 (comment) |
and others
UPDATED: selfhost has been released! Please refer to our selfhost tutorial. https://docs.affine.pro/docs/self-host-affine
If you have tried our docker before, don't forget to pull the image again.
If you encounter any problems, please open a new issue.
Many people are interested in the development of our new self-hosted version, so I created this issue to keep everyone updated on its progress.
The current version of docker image has lagged behind our stable branch for a long time. We need to update the new docker-image.
Since we ship many features like
paymentandaccounton the current backend server, it is not suitable for common self-hosted use cases. So we need to make these features optional in the new self-hosted version, which requires some work.Tasks
Archived issues
The text was updated successfully, but these errors were encountered: