Giter Club home page Giter Club logo

Comments (5)

dosubot avatar dosubot commented on September 12, 2024 2

Hey @johnfelipe! I'm here to help you with any bugs or questions you may have. I can assist with solving issues, answering questions, and becoming a contributor. Let me know how I can assist you!

To resolve the issue of the missing supabase/config.toml file, you need to create the config.toml file in the supabase directory with the appropriate configuration. Here is an example of what the config.toml file should look like:

# A string used to distinguish different Supabase projects on the same host. Defaults to the
# working directory name when running `supabase init`.
project_id = "secondbrain"

[api]
enabled = true
# Port to use for the API URL.
port = 54321
# Schemas to expose in your API. Tables, views and stored procedures in this schema will get API
# endpoints. public and storage are always included.
schemas = ["public", "storage", "graphql_public", "vault"]
# Extra schemas to add to the search_path of every request. public is always included.
extra_search_path = ["public", "extensions", "stripe", "vault"]
# The maximum number of rows returns from a view, table, or stored procedure. Limits payload size
# for accidental or malicious requests.
max_rows = 1000

[db]
# Port to use for the local database URL.
port = 54322
# Port used by db diff command to initialize the shadow database.
shadow_port = 54320
# The database major version to use. This has to be the same as your remote database's. Run `SHOW
# server_version;` on the remote database to check.
major_version = 15

[db.pooler]
enabled = false
# Port to use for the local connection pooler.
port = 54329
# Specifies when a server connection can be reused by other clients.
# Configure one of the supported pooler modes: `transaction`, `session`.
pool_mode = "transaction"
# How many server connections to allow per user/database pair.
default_pool_size = 20
# Maximum number of client connections allowed.
max_client_conn = 100

[realtime]
enabled = true
# Bind realtime via either IPv4 or IPv6. (default: IPv6)
# ip_version = "IPv6"
# The maximum length in bytes of HTTP request headers. (default: 4096)
# max_header_length = 4096

[studio]
enabled = true
# Port to use for Supabase Studio.
port = 54323
# External URL of the API server that frontend connects to.
api_url = "http://localhost"
# OpenAI API Key to use for Supabase AI in the Supabase Studio.
openai_api_key = "env(OPENAI_API_KEY)"

# Email testing server. Emails sent with the local dev setup are not actually sent - rather, they
# are monitored, and you can view the emails that would have been sent from the web interface.
[inbucket]
enabled = true
# Port to use for the email testing server web interface.
port = 54324
# Uncomment to expose additional ports for testing user applications that send emails.
# smtp_port = 54325
# pop3_port = 54326

[storage]
enabled = true
# The maximum file size allowed (e.g. "5MB", "500KB").
file_size_limit = "50MiB"

[auth]
enabled = true
# The base URL of your website. Used as an allow-list for redirects and for constructing URLs used
# in emails.
site_url = "http://localhost:3000"
# A list of *exact* URLs that auth providers are permitted to redirect to post authentication.
additional_redirect_urls = ["https://localhost:3000"]
# How long tokens are valid for, in seconds. Defaults to 3600 (1 hour), maximum 604,800 (1 week).
jwt_expiry = 3600
# If disabled, the refresh token will never expire.
enable_refresh_token_rotation = true
# Allows refresh tokens to be reused after expiry, up to the specified interval in seconds.
# Requires enable_refresh_token_rotation = true.
refresh_token_reuse_interval = 10
# Allow/disallow new user signups to your project.
enable_signup = true
# Allow/disallow testing manual linking of accounts
enable_manual_linking = false

[auth.email]
# Allow/disallow new user signups via email to your project.
enable_signup = true
# If enabled, a user will be required to confirm any email change on both the old, and new email
# addresses. If disabled, only the new email is required to confirm.
double_confirm_changes = true
# If enabled, users need to confirm their email address before signing in.
enable_confirmations = false

# Uncomment to customize email template
# [auth.email.template.invite]
# subject = "You have been invited"
# content_path = "./supabase/templates/invite.html"

Create this file in the supabase directory of your project, and then try running supabase migration up again [1].

To continue talking to Dosu, mention @dosu.

from quivr.

dosubot avatar dosubot commented on September 12, 2024 2

To resolve the issue where supabase migration up cannot read the supabase/config.toml file, try the following steps:

  1. Verify the File Path: Ensure that the supabase/config.toml file is indeed located at /home/felipe/Quivr/supabase/config.toml.

  2. Check Directory Structure: The directory structure should look like this:

    /home/felipe/Quivr/
    ├── supabase/
    │   └── config.toml
    
  3. Run supabase init: The error message suggests running supabase init to set up the project. This command initializes the Supabase project and creates the necessary configuration files. Run the following command in the Quivr directory:

    supabase init
  4. Permissions: Ensure that the file has the correct permissions and is readable by the user running the command. You can set the appropriate permissions using:

    chmod 644 /home/felipe/Quivr/supabase/config.toml
  5. Environment Variables: Ensure that the necessary environment variables are set. Copy the .env.example file to .env and update it with the correct values:

    cp .env.example .env
  6. Supabase CLI Version: Ensure you are using the correct version of the Supabase CLI. The Quivr repository specifies the version in its .devcontainer/devcontainer.json file as ghcr.io/devcontainers-contrib/features/supabase-cli:1. Check your current version with:

    supabase -v
  7. Run in Debug Mode: If the issue persists, try running the command in debug mode to get more detailed information:

    supabase migration up --debug

By following these steps, you should be able to resolve the issue and successfully run the supabase migration up command [1][2][3].

To continue talking to Dosu, mention @dosu.

from quivr.

linear avatar linear commented on September 12, 2024

TICK-37 [Bug]: update error

from quivr.

johnfelipe avatar johnfelipe commented on September 12, 2024

file is exactly same, pls give me more option for solve this issue:

felipe@template:~$ cd Quivr/
felipe@template:~/Quivr$ supabase migration up
cannot read config in /home/felipe/Quivr: open supabase/config.toml: no such file or directory
Have you set up the project with supabase init?

from quivr.

StanGirard avatar StanGirard commented on September 12, 2024

Hey my friend, please make sure you are in the backend folder when doing so 🙂

from quivr.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.