Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
755d1e1e
Commit
755d1e1e
authored
Mar 28, 2022
by
Jannik Lehmann
Committed by
Marcin Sedlak-Jakubowski
Mar 28, 2022
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Enhance act as saas docs
parent
1023f7c2
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
1 deletion
+6
-1
doc/development/ee_features.md
doc/development/ee_features.md
+6
-1
No files found.
doc/development/ee_features.md
View file @
755d1e1e
...
...
@@ -21,7 +21,12 @@ info: To determine the technical writer assigned to the Stage/Group associated w
When developing locally, there are times when you need your instance to act like the SaaS version of the product.
In those instances, you can simulate SaaS by exporting an environment variable as seen below:
`export GITLAB_SIMULATE_SAAS=1`
```
shell
export
GITLAB_SIMULATE_SAAS
=
1
```
There are many ways to pass an environment variable to your local GitLab instance.
For example, you can create a
`env.runit`
file in the root of your GDK with the above snippet.
## Act as CE when unlicensed
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment