Akumina Developer Documentation

Akumina Developer Documentation

  • API
  • Docs
  • Blog

›Azure DevOps

Akumina

  • Quickstart

Yo Akumina

  • Yo Akumina
  • Start with Yeoman
  • React
  • Simple template

Widget Builder

  • Widget Builder Structure
  • Akumina Widget Builder
  • Skipping instances
  • Token replacement for widget properties

Widget Development Quickstart

  • Setting up the Project
  • Configuring .env file
  • Configuring - akumina.sitedployer.config.json file
  • Configuring - akumina.config.json file
  • Extras

Widget Info

  • Akumina Widgets Overview
  • Building a New Widget Instance
  • Widget Views
  • Widget Properties
  • Global vs Local widgets (Widget Scoping)
  • Akumina React Widgets
  • Callbacks
  • RenderChildWidgets
  • Vendor Package List

Virtual Page Builder

  • Akumina Virtual Page Builder
  • Using Virtual Page Layouts
  • Creating a Custom Layout

Stream Card Builder

  • Installation
  • Stream Card Builder
  • Custom Cards
  • Activity Comments Config
  • Akumina Activity Stream PUSH Subscription using PowerAutomate to connect to ServiceNow
  • Akumina Activity Stream PUSH Subscription using PowerAutomate to connect to Dynamic 365

Site Deployer

  • Overview
  • Version 6.0
  • List Attribute Deployments
  • NPM Commands
  • SPA Updates and Deploying to multiple sites

Authoring

  • Content Action Event
  • Publish Validation Integration
  • Field Event Integration
  • CK Editor external plugins

Headless

  • Quickstart
  • Headless Teams support
  • Headless Troubleshooting

Modern

  • Overview
  • FAQ
  • Single Page Application
  • Modern Web Part Library
  • Google Analytics for Modern Pages

Site Creator

  • Overview
  • Adding A Custom Site Definition
  • Core Step Classes
  • Custom Site Definition Components
  • Custom Site Definition XML
  • Custom Subsite Definitions
  • Sample Step Code
  • Supported Tokens

Azure DevOps

  • CI/CD using Azure DevOps
  • Setting up a build to deploy a site package
  • Setting up a build to deploy file to App Manager hosted in an app service

Configuration

  • Configuration Context Overview
  • Edit the Redis cache timeout
  • Using a key vault for the client id and client secret

Debugging

  • Debugging in Akumina

Advanced

  • Central Site Collection Support
  • Eventing OOB Digital Workplace Events
  • Working with custom JSX Views
  • Page Indexing

Service Hub

  • Quickstart

Patch Notes

  • Patch Notes

Setting up a build to deploy file to App Manager hosted in an app service

Applies to

All versions of Akumina

Overview

This article describes how to create a build pipeline to deploy files to an Akumina App Manager, located in an app service.

To create a build

Go into Azure DevOps for the project you want. In our example we will use the code located in the TFS path:

$/BPS/Example/

Go to Pipelines -> Builds. Click New pipeline.

For our example we have code in TFS, so we use the visual designer option.

Select TFVC as the source, and then enter in the TFS path:

In the Build definition, click the plus icon (+) to add under Agent job 1. Then select FTP Upload from the list.

In the FTP Upload properties dialog, enter in a display name. Then in the FTP Service Connection field, select the ftp service connection. If you do not have one, click Manage.

If you have selected a service connection, skip this section.

Click New service connection and select generic.

Fill out the Add a generic service connection dialog with the proper values:

PropertyValue
Connection NameA common name for the connection
Server URLThe FTP server url
User nameThe user name to the FTP site
Password/Token KeyThe password to the FTP site

Then click OK.

After the service connection has been selected, you can then fill out the other values in the FTP Upload properties window.

PropertyValue
Root folderThe path to the files you want to upload into the app service.
File patternsThe pattern of file to select. Example: *.dll for all .dll files.
Remote directoryThe remote path for the file(s) to be uploaded. For an app service, the default path is /site/wwwroot

With the actions and the variables saved, we then need to Save. Click Save on the “Save build pipeline” dialog.

Once we save, we can then run the build – go back to builds, and either Run or Queue the build.

We can then separately queue up the build to run later, by returning to Pipelines -> Builds, and clicking the build. We can then queue it via the Queue button.

After the build runs, we will see that the files are deployed into the specified location in the app service.

References:

  • Site Deployer: Continuous Site Package Deployment via a console app
  • Site Deployer 4.1
← Setting up a build to deploy a site packageConfiguration Context Overview →
Akumina Developer Documentation
Docs
Akumina Framework 5.0Akumina Widget BuilderAkumina Yeoman GeneratorSite Deployer
Community
Akumina Community Site
More
GitHubStar
Copyright © 2024 Akumina