[GH-ISSUE #4011] [feature]: Ability to set default collections and environment for self-hosted hoops or h #1414

New issue

Open

opened 2026-03-16 20:15:56 +03:00 by kerem · 1 comment

kerem commented

2026-03-16 20:15:56 +03:00

Owner

Originally created by @mikeacjones on GitHub (Apr 27, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4011

Is there an existing issue for this?

I have searched the existing issues

Summary

For a self hosted instance of hoppscotch, the ability to add a default environment file and set of collections that load as the splash screen (rather than the echo endpoint) the first time a user navigates to the instance. The ability to auto-import a collection via query param almost works, but does not support the ability to assign a default environment with environment variables. Rather than forcing it to be loaded via a query param it would be more seamless to have something like a folder we can mount to the container that contains those default files.

Why should this be worked on?

The use case I have in mind is hosting the Hoppscotch server as part of a sandbox. The sandbox might be used by as many as 30 people during something like a capture the flag. So a shared workspace won’t work as everyone needs their own local “instance” of the collections. Having the collections and environment file something that can be loaded in by default would be ideal. Today I’m using the import functionality via URL, by embedding the URL in the instructions for participants, but it still requires users to then import the environment file and then manually set the environment.

Outside of my use case, this would make it far easier to self host hoppscotch as a kind of “try it now” button. Think similar to the way GraphiQL works on sites.

Originally created by @mikeacjones on GitHub (Apr 27, 2024). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4011 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Summary For a self hosted instance of hoppscotch, the ability to add a default environment file and set of collections that load as the splash screen (rather than the echo endpoint) the first time a user navigates to the instance. The ability to auto-import a collection via query param almost works, but does not support the ability to assign a default environment with environment variables. Rather than forcing it to be loaded via a query param it would be more seamless to have something like a folder we can mount to the container that contains those default files. ### Why should this be worked on? The use case I have in mind is hosting the Hoppscotch server as part of a sandbox. The sandbox might be used by as many as 30 people during something like a capture the flag. So a shared workspace won’t work as everyone needs their own local “instance” of the collections. Having the collections and environment file something that can be loaded in by default would be ideal. Today I’m using the import functionality via URL, by embedding the URL in the instructions for participants, but it still requires users to then import the environment file and then manually set the environment. Outside of my use case, this would make it far easier to self host hoppscotch as a kind of “try it now” button. Think similar to the way GraphiQL works on sites.