autoEdit 2 Documentation
1.0.13
1.0.13
  • Introduction
  • Overview
    • Intro
      • Development approach
      • from 1.0.5 to 1.0.6
    • Architecture Overview
      • Lo fi Design Sketches
      • High fidelity sketches in HTML
    • Support the project
    • documentation section template
    • Build / Deployment
      • Deployment/build for Mac OS X
      • Deployment / Build for Linux
      • Deployment / Build for Windows
      • Travis CI continuous build
        • previous travis setup
  • R&D Doc
    • About R&D doc section
    • Transcription & Media Processing
      • Transcription json
      • Transcriber
        • audio to video
        • STT sdks
          • IBM Watson STT
          • Gentle STT
          • Pocketsphinx
      • Video preview conversion
      • Read metadata
    • Hypertranscript
    • Selections, Annotations, Papercuts
      • Selections
      • Annotations
      • Tags
    • Paper-edit
      • Paper-edit json
      • search-filter
      • drag-and-drop
      • Preview Paper-edit video
    • Export
      • EDL export
      • XML export
      • mp4 export
  • Appendix
    • Dev configuration
    • Current db setup
    • EDL Format
    • Reusable components
    • Prerequisites
    • Testing
    • Updating automated documentation
    • ffmpeg and ffprobe in electron
    • Adding STT services
  • Appendix - Data structures
    • IBM Watson json specs
    • Gentle Json transcription specs
    • Pocketsphinx results
    • autoEdit transcription Json
  • QA List
    • QA Intro
  • Adobe Panel
    • autoEdit Adobe CEP Panel dev setup
      • Adobe Extensions HostList codes
    • autoEdit Adobe CEP Panel integration overview
    • Jsx functions for Adobe CEP autoEdit adobe Panel
    • Packaging and distributing Adobe CEP Extensions
      • Packaging signing Adobe CEP Panel in details
      • Submit to Adobe
  • Project Page
    • Build project page
    • Build/update demo front end page
  • Roadmap
    • Improvements
    • Roadmap
      • Paper-editing Roadmap
      • Extra Features Roadmap
      • Future Roadmap
        • Live video editing
        • Social Media Export
        • Translate transcriptions
        • Web app
          • Multi-user collaboration
        • Searchable Editable Archive
        • NLP insights
        • Slack/Chat bot integration
        • Interactive dev tool
        • Phone mms integration with twillio
        • B-roll computational photography
Powered by GitBook
On this page
  • What is an AppImage
  • Making it executable
  • Executing it
  • AppImage advantages
  1. Overview
  2. Build / Deployment

Deployment / Build for Linux

PreviousDeployment/build for Mac OS XNextDeployment / Build for Windows

Last updated 6 years ago

From terminal from root of app, run the deployment script

npm install

Then

npm run build:linux

It creates a cache and a build folder. cache is a folder used by deploy to keep the latest version needed to build and package the app, to avoid having to re-download it every time. While the packaged app ready for use can be found in the build folder.

It packages the app as a that works across linux distribution see deployment section and this and corresponding for more details.

Download an application, make it executable, and run! No need to install. No system libraries or system preferences are altered.

Distribute your desktop Linux application in the AppImage format and win users running all common Linux distributions. Package once and run everywhere. Reach users on all major desktop distributions.

AppImages can be downloaded and run without installation or the need for root rights.

Making it executable You can make the appImage executable as follows:

chmod a+x exampleName.AppImage Executing it You can execute an appImage as follows:

./exampleName.AppImage

What is an AppImage

AppImages can be downloaded and run without installation or the need for root rights.

Making it executable

You can make the appImage executable as follows:

chmod a+x exampleName.AppImage

Executing it

You can execute an appImage as follows:

./exampleName.AppImage

AppImage advantages

  • Applications packaged as an AppImage can run on many distributions (including Ubuntu, Fedora, openSUSE, CentOS, elementaryOS, Linux Mint, and others)

  • No unpacking or installation necessary

  • No root needed

  • No system libraries changed

  • Works out of the box, no installation of runtimes needed

  • Optional desktop integration with appimaged

  • Optional binary delta updates, e.g., for continuous builds (only download the binary diff) using AppImageUpdate

  • Can optionally GPG2-sign your AppImages (inside the file)

  • Works on Live ISOs

  • Can use the same AppImages when dual-booting multiple distributions

  • Can double as a self-extracting compressed archive with the --appimage-extract parameter

If you have questions, AppImage developers are on #AppImage on irc.freenode.net.

Or

Providing an would have, among others, these advantages:

One app = one file = super simple for users: just download one AppImage file, , and run

Can be listed in the central directory of available AppImages

of projects that are already distributing upstream-provided, official AppImages.

Fore more details on how to run in Linux after download this see below
see also how to make an AppImage executable for easier users instructions using GUI
AppImage
make it executable
AppImageHub
Here is an overview
AppImages
issue
PR
LogoLinux version · Issue #36 · OpenNewsLabs/autoEdit_2GitHub
LogoAppImage by probonopd · Pull Request #45 · OpenNewsLabs/autoEdit_2GitHub