Altostra Docs

›Commands

Getting Started

  • Welcome to Altostra
  • Connect your accounts
  • Install the developer tools
  • Log in from the CLI

Tutorials

  • Create a Static Website
  • Create a Scalable Webhook
  • Create a Simple API Project
  • CI/CD with Altostra CLI and Github Actions
  • Deploying a Project to Multiple Environments

How To

    Working with projects

    • Create a new project
    • Deploy a project
    • Manage a project

    Working with environments

    • Manage an environment
    • Configure stacks expiration for an environment

    Working with the Editor

    • Grant access to vendor services
    • Use the Parameter Store
    • Use a custom CloudFormation resource
    • Attach a custom policy to a Function
    • Connect a Function to VPC
    • Add filter policy to SNS subscription

    Organization account settings

    • Set General Settings
    • Connect a Git account
    • Connect Cloud Accounts
    • Manage log aggregation accounts

CLI

  • Altostra CLI
  • Commands

    • account
    • activity-log
    • api-key
    • build
    • config
    • console
    • deploy
    • docs
    • endpoints
    • environments
    • import
    • init
    • invalidate
    • login
    • logout
    • new
    • projects
    • push
    • deploy-cfn
    • deploy-sam
    • deploy-sls
    • stacks
    • sync
    • tasks
    • templates
    • versions
    • whoami

    Options

    • --debug
    • --verbose
    • Scripting options
  • Configuration files

Errors And Solutions

  • Autnentication Required

Technical Reference

  • Environments
  • Stacks
  • Projects
  • Versions Repository
  • Log Shipping
  • Deployment Modes
  • Altostra Cloud Integration

Integrations

    CI/CD

    • CircleCI

    Git

    • Git integration
    • Connect a GitHub account
    • Connect a Bitbucket account

    Messaging

    • Connect a Slack workspace

    Security

    • Connect an Auth0 tenant

sync

The alto sync command is used to upload files from the local application directory to their respective file-stores.

For example, you build a website that has a file-store resource that hosts the website content files. You would then use the alto deploy command to deploy the application infrastructure and the alto sync command to upload the files.

The command takes a stack to which the files should be uploaded, for example dev or prod.

You can either sync specific file-stores or all files-stores in an application by using the --all and --buckets options. These options are mutually exclusive.

By default, the files are not publicly accessible. To make the uploaded files public, use the --public option.

Usage

$ alto sync <stack-name>

Arguments

stack-name

The stack to which the files should be uploaded.

Options

--all

Sync all file-stores in the application.

Aliases: -a

Required: no

--buckets <list of file-stores>

Sync a given subset of file-stores in the application.

Aliases: -b

Required: no

--public

Make the uploaded files publicly accessible. By default, all files are not publicly accessible.

Required: no

--project-path

Specify the project working directory.

If not specified, project directory is assumed to be the current directory.

Aliases: --pp

Required: no

← stackstasks →
  • Usage
  • Arguments
    • stack-name
  • Options
    • --all
    • --buckets <list of file-stores>
    • --public
    • --project-path

Ready to Get Started?

Get Started for Free
© 2022 Altostra, Inc.