Documentation Remote Config Server Url

[mpaxson]

Validations

• I believe this is a way to improve. I'll try to join the Continue Discord for questions
• I'm not able to find an open issue that requests the same enhancement

Problem

I can't figure out how to setup the remote config server for continue,

I would like to setup an airgapped config server for my team and host the configurations remotely.

Is it possible to give some commands while I wait for the documentation to be updated?

Thanks !

Solution

No response

[aalvess]

Have you tried to set "apiBase" parameter?

Source: https://github.com/continuedev/continue/blob/main/core/llm/llms/Ollama.ts

[shashade2012]

Same comments for this remoteConfigServerUrl. How to use this?
I found this in Setting.
Remote Config Server Url
If your team is set up to use shared configuration, enter the server URL here and your user token below to enable automatic syncing.
But there is no information in guide.

[aalvess]

Hi, you can setup initially full offline than open the plugin tab and click in Configure COntinue:

than add the configuration:

[jasongwq]

This configuration seems to be an enterprise option.
You can try contacting enterprise support.：https://www.continue.dev/enterprise

continue/core/continueServer/stubs/client.ts

Line 14 in 16bfb95

throw new Error("Not Implemented");

[antoineauger]

This configuration seems to be an enterprise option.

Maybe @sestinj could confirm (or not) this information? 😁

[bufferoverflow]

@antoineauger I think we should contribute docs and co. to make it work according to https://amplified.dev/#5-adopt-open-source-interfaces , the maintainers might just be to busy with lot of stuff 👷 🔧

[changchiyou]

https://discord.com/channels/1108621136150929458/1247041256173993997

[mpaxson]

My use case it to create a .vscode/.settings.json in a git project that would point to a local hosted continue server. We use continue in an air gapped environment (no internet), so being able to share a .continue config for a project repo would be extremely useful for onboarding, quick starting, and enabling more people to use your tool.

I am trying to introduce more local ai in my company’s workflow and the biggest barrier to using continue believe it or not is time to setup/configure per box. It only matters if my team can easily use your tool, and I do believe that every project will have separate continue commands/prompts/api endpoints.

Being able to move the local users .continue config to a vscode settings or have a config server somewhere would be extremely useful.

[sestinj]

@bufferoverflow @antoineauger @mpaxson @jasongwq thanks for your patience here—we have been a bit busy with other work, but I didn't mean to wait to respond.

This is currently offered through our enterprise product, but we do want to make it more available because I understand that it is very useful. As @bufferoverflow said, we want to encourage open interfaces, but also wanted to get them right before shipping something we wouldn't be able to reverse. I apologize for the lack of extra information on what this update will be, but I will in fact have an update on this very soon

In the meantime, there are a couple of options that might be helpful:

• .continuerc.json has the same schema as config.json, but can be placed in the root of your GitHub repo as a means of sharing with others. Continue will notice it and apply the .continuerc.json on top of the user's config.json
• .prompt files are another way of sharing configuration. They don't do everything, just slash commands, but might be useful

[DanielAdari]

We're also in the exact same situation as @mpaxson and would greatly benefit from this feature!

[antoineauger]

Thanks for your response @sestinj! (this notification also slipped through my inbox)

Just let us know if you need help/early feedback on this, we will be happy to support you 😸

[ritamariavermelho06]

@bufferoverflow @antoineauger @mpaxson @jasongwq thanks for your patience here—we have been a bit busy with other work, but I didn't mean to wait to respond.

This is currently offered through our enterprise product, but we do want to make it more available because I understand that it is very useful. As @bufferoverflow said, we want to encourage open interfaces, but also wanted to get them right before shipping something we wouldn't be able to reverse. I apologize for the lack of extra information on what this update will be, but I will in fact have an update on this very soon

In the meantime, there are a couple of options that might be helpful:

• .continuerc.json has the same schema as config.json, but can be placed in the root of your GitHub repo as a means of sharing with others. Continue will notice it and apply the .continuerc.json on top of the user's config.json
• .prompt files are another way of sharing configuration. They don't do everything, just slash commands, but might be useful

@sestinj Thanks for the feedback and hard work, with your response I see that it has already been implemented and can be made available in the community version in the future? I was thinking of implementing something myself but if that's the plan then it would be best to wait ;)

[aidansommers]

Hello! Have there been any updates on if/when this would be available to the community? Thank you!

If anyone has alternative solutions they recommend for hosting on an air gapped server, that would be awesome.

Thank you to the community and team!

[bdavj]

Another +1 for this feature - it would be great to be able to centralise config.

[shohamyamin]

+1

[NestOne]

+1