Commit 4a2cccef authored by Thong Kuah's avatar Thong Kuah 🌏 Committed by Mike Greiling

Move tips and troubleshooting to bottom of doc

This is the usual place where I expect such info to be.
parent 47cb20b4
......@@ -191,15 +191,6 @@ test](https://gitlab.com/gitlab-org/gitlab-ce/blob/eb146e9abe08c3991b5a54237c24d
does teardown the K8s cluster at the end so after the test finishes it won't be
possible to run the pipeline again unless you comment this out.
## Tips, Troubleshooting and Useful Commands
Be sure to check out:
- [Auto DevOps - Tips and Troubleshooting](doc/howto/auto_devops/tips_and_troubleshooting.md)
- [Auto DevOps - Useful Commands](doc/howto/auto_devops/useful_commands.md)
They might save you a lot of time time during work.
## Technical Details and Alternatives
There are many ways to test out Auto DevOps and we have outlined hopefully one
......@@ -508,3 +499,12 @@ created by these automated tests. The disk name will start with
`gke-qa-cluster-`. Also note there will likely be many such disks here as our
automated tests do not clean these up after each run. It is a good idea to
clean them up yourself while you're on this page.
## Tips, Troubleshooting and Useful Commands
Be sure to check out:
- [Auto DevOps - Tips and Troubleshooting](doc/howto/auto_devops/tips_and_troubleshooting.md)
- [Auto DevOps - Useful Commands](doc/howto/auto_devops/useful_commands.md)
They might save you a lot of time time during work.
......@@ -16,10 +16,55 @@ assertion about
builds](https://gitlab.com/gitlab-org/gitlab-ce/blob/eb146e9abe08c3991b5a54237c24d15312c70ee8/qa/qa/specs/features/browser_ui/7_configure/auto_devops/create_project_with_auto_devops_spec.rb#L61)
to save yourself from setting up a full working Auto DevOps project.
- Set the environment variable `CHROME_REUSE_PROFILE` to `true` which
will allow QA to re-use the same user profile so that slow files such
as `main.chunk.js` can be cached in memory.
- Disable source-maps for GDK by setting the environment variable
`NO_SOURCEMAPS` to `true`. This reduces the size of `main.chunk.js`
from 11 MB to 4.6 MB, which will help for connections with slow upload speeds.
### Helm/Tiller Communication
- One can run manual Helm commands from your local machine and communicate to our remote Tiller running on GKE. Check our [Useful Commands - Talking to Tiller](./useful_commands.md#talking-to-tiller) to know how to achieve it.
## Development using localhost instead
Consider not using the internet-facing URL for non Auto DevOps flows,
but accessing your local GitLab instance via localhost. If you have
followed the [Auto DevOps setup](../auto_devops.md), edit the
`config/gitlab.yml` file to the following:
```yaml
host_settings_auto: &gitlab_auto_devops
host: <PORT>.qa-tunnel.gitlab.info
port: 443
https: true
host_settings_local: &gitlab_localhost
host: localhost
port: 80 # Set to 443 if using HTTPS, see installation.md#using-https for additional HTTPS configuration details
https: false # Set to true if using HTTPS, see installation.md#using-https for additional HTTPS configuration details
production: &base
#
# 1. GitLab app settings
# ==========================
## GitLab settings
gitlab:
## Web server settings (note: host is the FQDN, do not include http://)
# <<: *gitlab_auto_devops
<<: *gitlab_localhost
```
This way you can switch between using `*gitlab_localhost` for other
development and `*gitlab_auto_devops` for Auto-DevOps development.
Remember to restart your GDK after editing `config/gitlab.yml`.
NOTE: You will have to reapply the edits above after each `gdk
reconfigure`.
## Using an external virtual machine for the development
If you decide to use an external virtual machine to run GDK on it, you might
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment