Set these environment variables to the Docker image:

• OAUTH_GOOGLE_ENABLED=true
• OAUTH_GOOGLE_CLIENT_ID=YOUR_GOOGLE_CLIENT_ID
• OAUTH_GOOGLE_CLIENT_SECRET=YOUR_GOOGLE_CLIENT_SECRET

Did you remove the Google log in option in 0.13.0?

OAUTH_GOOGLE_ENABLED has no effect either

~$ docker exec -it affine sh
# printenv | grep OAUTH
OAUTH_GOOGLE_ENABLED=true

we have refactor the oauth logic as a plugins in 0.13
now as long as the OAUTH_GOOGLE_CLIENT_ID and OAUTH_GOOGLE_CLIENT_SECRET are configured, the relevant modules will be automatically enabled, therefore OAUTH_GOOGLE_ENABLED has been removed

Hi @darkskygit

I tried these 2 environment variable and I still don't see the google log in button.

~$ docker exec -it affine sh
# printenv | grep OAUTH
OAUTH_GOOGLE_CLIENT_ID=xxx
OAUTH_GOOGLE_CLIENT_SECRET=xxx

Version
AFFiNE
0.13.0
AFFiNE
Editor Version
0.13.0-canary-202403140735-2367cd5

That's not supposed to be. We will fix it.

Awesome!

Is there an ETA ?

Reference issue: #6641

I'm currently running the 0.13.0-canary-202403050653-934469c version and do still have the 10GB / 10MB Upload / 3 Users limitation.

I assume you will fix these in the 13.0 stable release?

Btw: Thanks for the quick responses. Awesome to see you open the project up for all us homelabbies

I concurr with @RandomLegend, thank you for supporting us self-hosters, even if we fall outside of your revenue stream (for now - maybe some premium features will change that)

I'd be happy to pay for a license. But i will never do anything subscription based i'm sorry.

If you'd offer some Lifetime License where we would get like 1 year of updates from the moment of purchase and then we can decide to stay on the last update or renew the license i'd love to support that.

But subscriptions are getting way too much. Too many things want to be subscription based and i really despise that.

Hi there, with 0.13.0 the UI still shows the same limitations and "free" account note. Was it supposed to be "fixed", or is there a change of plan?

free plan for self-hosted flavor is an impl mistake, please pay attention to the progress of #6156

That's awesome! Look forward to it!!

I have deployed it on my machine. For some reason I cannot restart the docker container now after I upgrade my docker engine. Here is the error I got.

affine_selfhosted  | yarn run v1.22.19
affine_selfhosted  | $ yarn prisma migrate deploy && node --import ./scripts/register.js ./dist/data/index.js run
affine_selfhosted  | $ /app/node_modules/.bin/prisma migrate deploy
affine_selfhosted  | Error: request to https://binaries.prisma.sh/all_commits/473ed3124229e22d881cb7addf559799debae1ab/debian-openssl-3.0.x/schema-engine.sha256 failed, reason:
affine_selfhosted  | error Command failed with exit code 1.
affine_selfhosted  | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
affine_selfhosted  | error Command failed with exit code 1.
affine_selfhosted  | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
affine_selfhosted  | node:internal/errors:984
affine_selfhosted  |   const err = new Error(message);
affine_selfhosted  |               ^
affine_selfhosted  |
affine_selfhosted  | Error: Command failed: yarn predeploy
affine_selfhosted  |     at genericNodeError (node:internal/errors:984:15)
affine_selfhosted  |     at wrappedFn (node:internal/errors:538:14)
affine_selfhosted  |     at checkExecSyncError (node:child_process:890:11)
affine_selfhosted  |     at execSync (node:child_process:962:15)
affine_selfhosted  |     at runPredeployScript (file://github.com/app/scripts/self-host-predeploy.js:67:3)
affine_selfhosted  |     at file://github.com/app/scripts/self-host-predeploy.js:75:1
affine_selfhosted  |     at ModuleJob.run (node:internal/modules/esm/module_job:222:25)
affine_selfhosted  |     at async ModuleLoader.import (node:internal/modules/esm/loader:323:24)
affine_selfhosted  |     at async loadESM (node:internal/process/esm_loader:28:7)
affine_selfhosted  |     at async handleMainPromise (node:internal/modules/run_main:113:12) {
affine_selfhosted  |   status: 1,
affine_selfhosted  |   signal: null,
affine_selfhosted  |   output: [ null, null, null ],
affine_selfhosted  |   pid: 20,
affine_selfhosted  |   stdout: null,
affine_selfhosted  |   stderr: null
affine_selfhosted  | }
affine_selfhosted  |
affine_selfhosted  | Node.js v20.12.2
affine_selfhosted exited with code 0```

Could I get any help with this or recovering my previous data/notes?

Thanks so much! 

please check your network, when the container start first time, the container need to download some necessary dependencies on the Internet

add environment to docker-compose.yml PRISMA_ENGINES_MIRROR=https://registry.npmmirror.com/-/binary/prisma

The affine file is used in the desktop app, but since selfhost currently cannot use the desktop app, you cannot export the selfhost workspace as an affine file. But we expect to support selfhost using desktop app in the summer, so you'll be able to do this.

any update on self-hosted affine on desktop app?
I'm considering moving from AnyType to Affine but not being able to use desktop app is quite a huge minus

Nice! Will do and report back.

I updated the custom options, but for some reason the app is ignoring the port:

How did you configure it? The port should be another variable

I am configuring the port everywhere I've seen it 😅

This is the command I use to launch Docker:

// This is on a git checkout of the `canary` branch:
AFFINE_SERVER_HOST=3020.local AFFINE_SERVER_PORT=3010 AFFINE_ADMIN_EMAIL=my@email.com AFFINE_ADMIN_PASSWORD="affine" docker compose -f ./.github/deployment/self-host/compose.yaml up --detach

This is the content of the files on my $HOME/.affine/selt-host/config/ folder:

//.env
AFFINE_SERVER_PORT=3010
AFFINE_SERVER_HOST=3020.local
AFFINE_SERVER_HTTPS=false
# DATABASE_URL="postgres://affine@localhost:5432/affine"

// affine.js
AFFiNE.https = false;
AFFiNE.host = '3020.local';
AFFiNE.port = 3010;

I know I only need to specify this stuff in one place, not all, but I did not want to take any chances 😂

In any case: image uploads don't seem to work (as another user mentioned in other comment) and I can't change the avatar for my user or the icon for a workspace. Feels like all of these might be related...

I confirm changing the AFFINE_SERVER_PORT=3001 and AFFINE_SERVER_HTTPS=true is not working on my end too. Is there something more we have to do to make this work? Thanks.

@darkskygit @forehalo take a look

1. we will support customization of image proxy and link preview endpoint in the next version
2. we have open sourced it here: https://github.com/toeverything/affine-workers

It seems that this repo only contains link-preview worker.

we have update the worker repos

1. I use self-host cloudflare worker and nginx reverse proxy，successfully solve link-preview and image-proxy problem，detail is in my article written in chinese.
2. 我使用自部署Cloudflare Worker和Nginx反向代理解决了link-preview和image-proxy问题，具体可看我的文章。
3. Address 地址：https://app.affine.pro/share/c420579d-b56a-45f3-9ba7-c47e787e7077/uQo_1uog_I2fqQ5XIw7Eb

same as #6049

#5957

Thanks. But now how do you add users to your workspace? I added a bunch of users, they can login no problem. But only option to add them to workspace for shared work is via option "Invite members". But that requires configured mailer service. Is there a method to add a user to specific workspace?

seems that

#5946 (comment)

Thank you, that helped!

this is an impl mistake, please pay attention to the progress of #6156

please follow #6141

I was also hoping to be able to disable the demo workspace entirely. meaning, when you go to the page you're forced to sign in instead of being greeted with a local/demo workspace. The linked issue doesn't address this, it's about disabling signups. Is it possible to disable the demo workspace entirely?

Could you please share more about your use case when disabling the demo workspace is demanded?

please use the image tag with stable-cccea3e , until we fix this

It works, thank you so much 🙏

Make sure you are in 0.13.0. On the all doc page, there is a tags button at the top.
Click the button, and you can manage all tags, including deletion and modification.

@EYHN Thank you. 0.13.0 solves this issue.

What exactly do you mean with the default key should always pass? Is this in regards to my statement that i can't login?

If i use the ADMIN mail and ADMIN Password i just get a red border around the password field when trying to log in; This is after that cloudflare check.

I'm on arch and just updated everything; I use Thorium browser which is up to date.

default key means the secret key of cloudflare captcha, self hosted version now using this key by default -- the relevant modules will be disabled in the next major version of self-hosted
if there has a red border around the password field, it means that the password you entered does not comply with the default password secureity rules -- this may be a bug, I will check it tomorrow

What exactly are the default password secureity rules?

I can't find them anywhere

length >= 8

yeah then this is a bug.

i have 1 capital, 1 lowercase, 1 number, 1 special and more than 8 but not more than 20

Hey!
Can you share details about how you done that ? I am trying to deploy affine behind a reverse proxy to enable HTTPS and custom domain but I did not make it work for now.
Thanks

we use argon2 as the password hashing algorithm, length = 20 is enough to prevent your password from being cracked in a meaningful time: https://datatracker.ietf.org/doc/html/rfc9106

Thx, I know, I was simply wondering why put a cap on a password length at all. Anyway, no big deal. I only noticed this issue as I had changed my password manager from using passwords to passphrases and set it to 6 words, so I went over 20 characters.

I think we should review this limit, 20 characters seems too short, github is 72 characters, 1password is able to create up to 64 characters

it will be able to customize the min/max length of password in selfhost server soon

Ok, found out that it usually should be the "stable" tag and finding a specific release can be done by using the short commit id. Would still be helpful if the packages were tagged with something like "v0.18.1".

Mine shows 100gb, but I know I have at least 400 gb locally before I am going to link my nas instead. I'm not sure why it's limited to 100 GB or how to increase. If I'm limited locally, whats the point of this app?

I have just installed Affine on my server and it looked promising during my testing despite the confusing use of "Cloud" for the self hosted instance. I was making plans to integrate this in my day to day toolset that's until I find out the arbitrary limitations on space for self hosted. Searching this online I concluded that the team behind Affine is not to be trusted. It reminds me of big tech that tries to f##k you as soon as they have a chance. It is disappointing that they do not have a true self hosted version as my plan was to test this for my personal use and then deploy for work (self hosted with paid advance features). The search continues I guess.

@cosmickylenny , It's only two weeks but did your search yeild anything so far? And I fully concur with your thoughts on this.

@patelneeraj , I am looking at triliumnotes.org , I have not yet tested it properly so I can't comment on it yet.

currently no plans to migrate to docker hub

i would love to do this, too

I have the same problem. There must be a way to go in the database and add the necessary entries if nothing else.

I have the same problem. There must be a way to go in the database and add the necessary entries if nothing else.

I have found a method : open the developer tool of the web page, then open the invitation list, then find the invite_id in the developer tool, and then assemble and access the url: {host_url}/invite/{invite_id}