Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • D Desastres
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Desastres
  • Desastres
  • Wiki
  • setting enviroment

setting enviroment · Changes

Page history
Update setting enviroment authored Oct 29, 2018 by João Vitor Bernardi Severo's avatar João Vitor Bernardi Severo
Hide whitespace changes
Inline Side-by-side
setting-enviroment.md
View page @ ffa987d3
......@@ -37,8 +37,8 @@ If the virtual enviroment was not already set by the IDE, you must configure it
1. Opening the IDE you can use the shortcut `ctrl + alt + s` to open the project settings
2. Once popped up on the screen, open the `Project: Desastres` tab
3. Select `Project Interpreter`
4. On the left side of the path to the current virtual enviroment or the '<No interpreter>' field, click on the engine and `Add...`
4. On the right side of the path to the current virtual enviroment or the '<No interpreter>' field, click on the engine and `Add...`
5. Select the `Existing enviroment` radio button
6. On the left side of "<No interpreter>" or the old path of the enviroment, select the `...` button and chose the path to the interpreter
6. On the right side of "<No interpreter>" or the old path of the enviroment, select the `...` button and chose the path to the interpreter
Tip: The interpreter probably is inside the `.virtualenvs` folder created on your user profile
Clone repository
  • API
  • QuickStart
  • agents
  • agents
    • actions
    • agent
  • api
    • firstconnection
    • firstmessage
    • how it works
    • stepsmessages
  • Home
  • notes
  • requirements
  • setting enviroment
  • simulation
  • simulation
    • corearchitecture
View All Pages