1
0
mirror of https://github.com/bitwarden/server.git synced 2024-12-27 17:47:37 +01:00
The core infrastructure backend (API, database, Docker, etc).
Go to file
Colton Hurst ed1406acc2
[SM-90] Add Config Endpoint Phase 1 (#2130)
* Add config endpoint with version and gitHash in response

* Remove gitHash from version, formatting and other improvements

* change name of variable in ConfigController

* Update to properly get gitHash

* SM-94: Add global settings for api url

* SM-94: ConfigController cleanup

* SM-94: Make version and gitHash available for all projects, using AssemblyHelper

* Update ConfigResponseModel GetVersion() call

* Change AssemblyHelpers.cs to use the UTF-8 charset

* SM-94: Use AssemblyHelpers.GetVersion and deprecate CoreHelpers.GetVersion

* SM-90: Add other BaseServiceUriSettings urls

* SM-94: Fix dotnet format issue

* remove old GetVersion method

* Add back the linebreak

* Fix typo in Directory.Build.props

Co-authored-by: Oscar Hinton <Hinton@users.noreply.github.com>

Co-authored-by: Oscar Hinton <Hinton@users.noreply.github.com>
2022-09-05 11:19:04 -04:00
.config [PS-40] Upgrade to .NET 6 (#2056) 2022-06-24 10:39:34 -04:00
.github [EC-505] Update PR template (#2221) 2022-08-31 08:46:59 +10:00
.vscode Fix VSCode Launch file (#2077) 2022-06-26 10:03:33 -04:00
bitwarden_license [SM-90] Add Config Endpoint Phase 1 (#2130) 2022-09-05 11:19:04 -04:00
dev Reverse proxy / load balancer configuration for local development (#2097) 2022-08-31 17:21:40 -07:00
scripts New Self Host Stub Scripts (#1893) 2022-03-01 16:19:09 -05:00
src [SM-90] Add Config Endpoint Phase 1 (#2130) 2022-09-05 11:19:04 -04:00
test [EC-502] Rate Limiting Improvements (#2231) 2022-08-31 14:17:29 -07:00
util Run formatting (#2230) 2022-08-29 16:06:55 -04:00
.editorconfig Feature/bit auto data (#2219) 2022-08-31 08:38:35 -05:00
.git-blame-ignore-revs Add instructions (#2232) 2022-08-30 12:17:17 -04:00
.gitattributes Run dotnet format (#1764) 2021-12-16 15:35:09 +01:00
.gitignore revamping the build scripts (#1620) 2021-10-08 09:53:56 -07:00
bitwarden-server.sln [SM-153] Add scaffolded API integration test project (#2209) 2022-08-29 16:24:52 +02:00
CONTRIBUTING.md Update README and CONTRIBUTING to point to contributing.bitwarden.com (#2028) 2022-06-09 12:00:58 +02:00
Directory.Build.props [SM-90] Add Config Endpoint Phase 1 (#2130) 2022-09-05 11:19:04 -04:00
LICENSE_AGPL.txt split license file out to support bitwarden licensed code (#912) 2020-09-04 13:36:22 -04:00
LICENSE_BITWARDEN.txt Update LICENSE_BITWARDEN.txt 2021-03-26 14:08:09 -04:00
LICENSE_FAQ.md [SM-142] Rename CommCore to Commercial.Core (#2158) 2022-08-02 20:41:18 +02:00
LICENSE.txt Update LICENSE.txt 2021-03-26 14:09:28 -04:00
NuGet.Config initial commit of source 2015-12-08 22:57:38 -05:00
README.md Add instructions (#2232) 2022-08-30 12:17:17 -04:00
SECURITY.md Update SECURITY.md (#1913) 2022-03-15 15:54:08 -04:00
TRADEMARK_GUIDELINES.md Update TRADEMARK_GUIDELINES.md 2021-03-26 14:04:27 -04:00

Bitwarden

Github Workflow build on master DockerHub gitter chat


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.

Developer Documentation

Please refer to the Server Setup Guide in the Contributing Documentation for build instructions, recommended tooling, code style tips, and lots of other great information to get you started.

Deploy

docker

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

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

We're Hiring!

Interested in contributing in a big way? Consider joining our team! We're hiring for many positions. Please take a look at our Careers page to see what opportunities are currently open as well as what it's like to work at Bitwarden.

Contribute

Code contributions are welcome! Please commit any pull requests against the master branch. Learn more about how to contribute by reading the Contributing Guidelines. Check out the Contributing Documentation for how to get started with your first contribution.

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.

Dotnet-format

We recently migrated to using dotnet-format as code formatter. All previous branches will need to updated to avoid large merge conflicts using the following steps:

  1. Check out your local Branch
  2. Run git merge 61dc65aa598b1f492d2f0222bb7bf0dd15d116f5
  3. Resolve any merge conflicts, commit.
  4. Run dotnet tool run dotnet-format
  5. Commit
  6. Run git merge -Xours 23b0a1f9df25058ab29785ecad9a233113c10889
  7. Push

File Scoped Namespaces

We recently migrated to using file scoped namespaces to save some horizontal space. All previous branches will need to update to avoid large merge conflicts using the following steps:

  1. Check out your local Branch
  2. Run git merge 9b7aef0763ad14e229b337c3b5b27cb411009792
  3. Resolve any merge conflicts, commit.
  4. Run dotnet format
  5. Commit
  6. Run git merge -Xours 7f5f010e1eea400300c47f776604ecf46c4b4f2d
  7. Fix Merge conflicts
  8. Push