Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fetch Vault from upstream when building Docker image #2

Merged
merged 1 commit into from
Apr 18, 2018

Conversation

mprasil
Copy link
Contributor

@mprasil mprasil commented Apr 18, 2018

Hi, this extends the Dockerfile and builds the Vault files straight from upstream, so you can switch it easily. Should make it easier to follow the upstream.

@dani-garcia dani-garcia merged commit 8a0eac8 into dani-garcia:master Apr 18, 2018
@dani-garcia
Copy link
Owner

Thanks again mprasil!

@mprasil mprasil deleted the upstream-vault branch April 18, 2018 15:02
dani-garcia pushed a commit that referenced this pull request Jul 31, 2018
Sync local fork with upstream
BlackDex added a commit to BlackDex/vaultwarden that referenced this pull request Jan 31, 2021
Updated several json response models.
Also fixed a few small bugs.

ciphers.rs:
  - post_ciphers_create:
    * Prevent cipher creation to organization without a collection.
  - update_cipher_from_data:
    * Fixed removal of user_uuid which prevent user-owned shared-cipher to be not editable anymore when set to read-only.
    * Cleanup the json_data by removing the `Response` key/values from several objects.
  - delete_all:
    * Do not delete all Collections during the Purge of an Organization (same as upstream).

cipher.rs:
  - Cipher::to_json:
    * Updated json response to match upstream.
    * Return empty json object if there is no type_data instead of values which should not be set for the type_data.

organizations.rs:
  * Added two new endpoints to prevent Javascript errors regarding tax

organization.rs:
  - Organization::to_json:
    * Updated response model to match upstream
  - UserOrganization::to_json:
    * Updated response model to match upstream

collection.rs:
  - Collection::{to_json, to_json_details}:
    * Updated the json response model, and added a detailed version used during the sync
  - hide_passwords_for_user:
    * Added this function to return if the passwords should be hidden or not for the user at the specific collection (used by `to_json_details`)

Update dani-garcia#1: Some small changes after comments from @jjlin.
Update dani-garcia#2: Fixed vault purge by user to make sure the cipher is not part of an organization.

Resolves dani-garcia#971
Closes dani-garcia#990, Closes dani-garcia#991
thelittlefireman pushed a commit to thelittlefireman/bitwarden_rs that referenced this pull request Mar 19, 2021
Fetch Vault from upstream when building Docker image
thelittlefireman pushed a commit to thelittlefireman/bitwarden_rs that referenced this pull request Mar 19, 2021
dani-garcia pushed a commit that referenced this pull request Jan 9, 2023
dfunkt referenced this pull request in dfunkt/vaultwarden May 2, 2024
Fetch cargo dependencies only for the build platform, cross-compiling for the rest
dfunkt referenced this pull request in dfunkt/vaultwarden May 2, 2024
Fetch cargo dependencies only for the build platform, cross-compiling for the rest
dfunkt referenced this pull request in dfunkt/vaultwarden May 2, 2024
Fetch cargo dependencies only for the build platform, cross-compiling for the rest
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants