Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
Pixel Diary
Pixel Diary
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 10
    • Issues 10
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Dustin Eckhardt
  • Pixel DiaryPixel Diary
  • Wiki
  • Home

Last edited by Dustin Eckhardt Oct 09, 2019
Page history

Home

Space Usage

By default, Pixel Diary will save all diary data in the storage provided by the visitors browser. However, the available space of this storage may vary between browsers (typically 5-10 MB), but should be enough to store multiple years.

To put this seemingly small space in relation, the following table shows the space required for a full year.

Plain Encrypted Data Included
Minimal ~ 6 KB ~ 8 KB Only moods; no notes
Maximal ~ 60 KB ~ 80 KB A note with maximal length on every day

So, even if a browser would only offer 1 MB of space, it would be enough for 12.5 years of encrypted diary data (or ~16.5 if unencrypted).

Cloud Storage Registration

In order to use any of the supported cloud storages when hosting a Pixel Diary under your own domain, you will need to register your Pixel Diary at the respective providers. If you only host your Pixel Diary on your own machine, under http://localhost, you don't need to change anything.

Dropbox
  1. Create a new app using the App Console
  2. Select "Dropbox API" and "App folder", choose a name for your app, and then click "Create app"
  3. Now add the domain(s) of your Pixel Diary as "Redirect URIs"
  4. Click the "Enable additional users" button to allow other users to use your app
  5. Copy the "App key" and paste it into .env as the value of REACT_APP_CLOUD_DROPBOX
  6. And lastly, run npm run build (again) to apply the new configuration

Please note that you have to apply for production once your Pixel Diary links to 50 unique users. Details on this can be found in Dropbox's Developer Guide.

OneDrive
  1. Register a new app using Microsoft Azure
  2. Choose a name for your app
  3. Select "Accounts in any organizational directory and personal Microsoft accounts", if not already selected
  4. Add the domain(s) of your Pixel Diary as "Redirect URI", using the type "Web"
  5. Then click "Register"
  6. Copy the "Application (client) ID" from the overview and paste it into .env as the value of REACT_APP_CLOUD_ONEDRIVE
  7. Select "API permissions" on the sidebar and then click the "Add a permission" button
  8. Now select "Microsoft Graph" (typically the top most box), then select "Delegated permissions", and check the Files.ReadWrite.AppFolder permission
  9. Confirm the selection by clicking the "Add permission" button
  10. Select "Authentication" on the sidebar
  11. Now check the "Access tokens" option and apply the changes by clicking the "Save" button at the top
  12. And lastly, run npm run build (again) to apply the new configuration
Google Drive
  1. Create a new project using the API Console. Enter a project name and then click "Create"
  2. Select your project in top bar, if it isn't already selected
  3. Click the "Enable APIs and services" button
  4. Select "Google Drive API" and click "Enable"
  5. Click the "Create credentials" button in the top right
  6. Now return to your projects dashboard by clicking the Google APIs logo in the top left
  7. Select "OAuth consent screen" on the sidebar
  8. Choose a name for your app and add the domain(s) of your Pixel Diary as "Authorized domains"
  9. Click the "Add scope" button, check the ../auth/drive.appdata scope, and confirm by clicking "Add"
  10. Apply all changes by clicking the "Save" button
  11. Now select "OAuth client ID" from the "Create credentials" drop-down
  12. Select "Web application" and add the domain(s) of your Pixel Diary as "Authorized JavaScript origins" and as "Authorized redirect URIs", then click "Create"
  13. Copy the client ID and paste it into .env as the value of REACT_APP_CLOUD_GOOGLE_DRIVE
  14. And lastly, run npm run build (again) to apply the new configuration
Clone repository

Space Usage

Cloud Storage Registration

  • Dropbox
  • OneDrive
  • Google Drive