Help us learn about your current experience with the documentation.
Take the survey.
Configure the Gitpod development environmentTo contribute code without the overhead of setting up a local development environment, you should use Gitpod.
Use Gitpod to contribute without a local environment setupSet aside about 15 minutes to launch the GDK in Gitpod.
Select Continue with GitLab to start a Gitpod environment for this fork.
If this is your first time using Gitpod, create a free account and connect it to your GitLab account:
Browser
version of VS Code when prompted to Choose an editor.On the New Workspace screen, before you select Continue:
Leave the default repository URL: gitlab.com/gitlab-community/gitlab/-/tree/master/
.
Select your preferred Editor.
The examples in this tutorial use Visual Studio Code (VS Code) as the editor, sometimes referred to as an integrated development environment (IDE).
Leave the default Class: Standard
.
Wait a few minutes for Gitpod to launch.
You can begin exploring the codebase and making your changes after the editor you chose has launched.
You will need to wait a little longer for GitLab to be available to preview your changes.
When the GitLab GDK is ready, the Terminal panel in Gitpod will return a URL local to the Gitpod environment:
=> GitLab available at http://127.0.0.1:3000.
Select the http://127.0.0.1:3000
to open the GitLab development environment in a new browser tab.
After the environment loads, sign in as the default root
user and follow the prompts to change the default password:
root
5iveL!fe
After the Gitpod editor is ready, continue to Change the code with Gitpod.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4