eb3e318d33
* updating the qa deploy to dynamically pull the publish profile instead of proxying it through a key vault * fixing the download-artifact hash * fixing typo * trying out the custom keyvault getter * fixing the new deploy matrix * fixing the custom action path * setting custom action commit hash * paramaterized the deploy job * adding the staging slot to the publish profiles * trying a custom way to pull the publishing profile * removing the publish profile altogether since it might not even be needed * removing unnecessary publish profile stuff * removing the subscription id from the qa deploy workflow * adding auto swap for QA identity * adding the rest of the webapp slot swapping automation * fixing the job dependencies * fixing the matrix name variable and adding some debugging code * removing admin and identity out of the matrix swap * switching the alive check * fixing the identity endpoint * fixing the while loops * adding in sleeps to see if it is a matrix issue * running the matrix sequentially to see if that rids us of the slot swapping conflits * removing the sleep command in the matrix * removing the sequential controller * disabling the build and deploy for swapping tests * changing the live test a bit * fixing the identity status url * adding in a fail safe if not hit the alive endpoint * fixing the azure secret names * removing the debugging code * Update QA Deploy Workflow (#1387) * Testing workflow * Add whitespace to workflow Co-authored-by: Vince Grassia <593223+vgrassia@users.noreply.github.com> |
||
|---|---|---|
| .github | ||
| bitwarden_license | ||
| scripts | ||
| src | ||
| test | ||
| util | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| bitwarden-server.sln | ||
| CONTRIBUTING.md | ||
| Directory.Build.props | ||
| dotnet-tools.json | ||
| ISSUE_TEMPLATE.md | ||
| LICENSE_AGPL.txt | ||
| LICENSE_BITWARDEN.txt | ||
| LICENSE_FAQ.md | ||
| LICENSE.txt | ||
| NuGet.Config | ||
| README.md | ||
| SECURITY.md | ||
| SETUP.md | ||
| TRADEMARK_GUIDELINES.md | ||
The Bitwarden Server project contains the APIs, database, and other core infrastructure items needed for the "backend" of all bitwarden client applications.
The server project is written in C# using .NET Core with ASP.NET Core. The database is written in T-SQL/SQL Server. The codebase can be developed, built, run, and deployed cross-platform on Windows, macOS, and Linux distributions.
Build/Run
Please read the Setup guide for a step-by-step guide to set up your own local development server.
Requirements
These dependencies are free to use.
Recommended Development Tooling
- Visual Studio (Windows and macOS)
- Visual Studio Code (other)
These tools are free to use.
API
cd src/Api
dotnet restore
dotnet build
dotnet run
visit http://localhost:4000/alive
Identity
cd src/Identity
dotnet restore
dotnet build
dotnet run
visit http://localhost:33657/.well-known/openid-configuration
Deploy
You can deploy Bitwarden using Docker containers on Windows, macOS, and Linux distributions. Use the provided PowerShell and Bash scripts to get started quickly. Find all of the Bitwarden images on Docker Hub.
Full documentation for deploying Bitwarden with Docker can be found in our help center at: https://help.bitwarden.com/article/install-on-premise/
Requirements
- Docker
- Docker Compose (already included with some Docker installations)
These dependencies are free to use.
Linux & macOS
curl -s -o bitwarden.sh \
https://raw.githubusercontent.com/bitwarden/server/master/scripts/bitwarden.sh \
&& chmod +x bitwarden.sh
./bitwarden.sh install
./bitwarden.sh start
Windows
Invoke-RestMethod -OutFile bitwarden.ps1 `
-Uri https://raw.githubusercontent.com/bitwarden/server/master/scripts/bitwarden.ps1
.\bitwarden.ps1 -install
.\bitwarden.ps1 -start
Contribute
Code contributions are welcome! Visual Studio or VS Code is highly recommended if you are working on this project. Please commit any pull requests against the master branch. Please see CONTRIBUTING.md for more info (and feel free to contribute to that guide as well).
Security audits and feedback are welcome. Please open an issue or email us privately if the report is sensitive in nature. You can read our security policy in the SECURITY.md file. We also run a program on HackerOne.
No grant of any rights in the trademarks, service marks, or logos of Bitwarden is made (except as may be necessary to comply with the notice requirements as applicable), and use of any Bitwarden trademarks must comply with Bitwarden Trademark Guidelines.