2023-11-16 15:49:43 +05:00
2023-04-15 09:57:50 +08:00
2023-07-27 23:22:08 +02:00
2023-11-02 23:26:32 +01:00
2023-11-03 12:23:14 +01:00
2023-06-05 09:23:42 +02:00
2023-11-16 15:49:43 +05:00
2023-11-14 00:19:15 +01:00
2023-11-03 12:15:39 +01:00
2023-11-16 15:49:43 +05:00
2023-04-15 09:57:50 +08:00
2023-10-30 23:51:53 +01:00
2023-11-09 13:16:50 -03:00
2019-10-14 11:55:12 +02:00
2023-10-18 09:40:00 +02:00
2023-08-16 20:31:14 +02:00
2022-02-12 13:17:49 +01:00
2023-06-23 00:27:04 +08:00
2023-10-18 09:40:00 +02:00
2023-09-21 12:29:11 +02:00
2020-04-15 21:49:36 +02:00
2017-12-10 21:13:39 -05:00
2023-04-15 17:58:40 +08:00
2023-11-16 15:49:43 +05:00
2023-11-14 00:57:51 +01:00
2023-03-26 20:34:46 +09:00
2023-03-26 20:33:59 +09:00
2023-11-16 15:49:43 +05:00
2023-03-26 20:34:46 +09:00
2020-05-24 19:34:52 +02:00
2022-05-24 21:34:32 +02:00
2023-04-15 17:45:10 +08:00

Getting Started

Follow these instructions to run project locally.

Prerequisites

Follow these commands to run project successfully.

  • npm

    npm install npm@latest -g
    
    • or install yarn

Installation

  1. Clone the repo

    git clone https://github.com/magnusmage/magescribe.git
    
  2. Install packages in root directory

    npm install
    npm run start-server
    
  3. All done 😄😄

🎁 Features

Check out awesome-trilium for 3rd party themes, scripts, plugins and more.

🏗 Builds

Magescribe is provided as either desktop application (Linux and Windows) or web application hosted on your server (Linux). Mac OS desktop build is available, but it is unsupported.

  • If you want to use magescribe on the desktop, download binary release for your platform from latest release, unzip the package and run magescribe executable.
  • If you want to install Magescribe on server, follow this page.
    • Currently only recent Chrome and Firefox are supported (tested) browsers.

Magescribe is also provided as a Flatpak:

Usage

For additional usage read docs.

Contributing

For contributions greatly appreciated.

  1. Clone the Project
  2. Create your Feature Branch (git checkout -b feature/NewFeature)
  3. Commit your Changes (git commit -m 'Add: NewFeature')
  4. Push to the Branch (git push origin feature/NewFeature)
  5. Open a Pull Request

How to commit

For commit use prefixes in commit messages to provide context and clarity about the changes made to the code. This convention involves using short, descriptive prefixes such as

  • Add: for new features
  • Update: for modifications to existing functionality
  • Improvement: for code improvements
  • Fix: for bug fixes
  • Integration: for integration
  • Remove: for deleting code or features
  • Docs: for documentation updates

By following a consistent commit message convention, developers can efficiently track changes to the code and easily understand the navigate of modifications made over time.

License

Distributed under the MIT License. See LICENSE for more information.

Contact

https://magnusmage.com/

Copyright © 2023 — https://magnusmage.com/
Languages
JavaScript 98.4%
CSS 1%
EJS 0.3%
Shell 0.2%