[{"_1":2,"_160":-5,"_161":-5},"loaderData",{"_3":4,"_17":18,"_25":26,"_139":140},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7,"_13":14,"_15":16},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","theme","system","contrast","normal","routes/_layout",{"_19":-5,"_20":21,"_22":21,"_23":11,"_24":21},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_27":28,"_29":-5,"_30":11,"_31":11,"_32":33,"_34":35,"_36":-5,"_37":11,"_38":39,"_88":-5,"_89":90,"_128":-5,"_129":11,"_130":21,"_131":11,"_132":-5,"_133":11,"_134":-5,"_135":136,"_137":91,"_138":-7},"canonicalUrl","https://hub.docker.com/r/tylerlu/demoapp-base/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","tylerlu","reponame","demoapp-base","cloudBuildSource","isAutobuildsAvailable","repo",{"_40":41,"_42":43,"_45":46,"_47":48,"_49":11,"_50":51,"_52":53,"_54":55,"_57":35,"_32":33,"_58":59,"_60":44,"_61":62,"_63":64,"_65":66,"_67":-5,"_68":62,"_69":70,"_71":11,"_72":33,"_73":74,"_79":11,"_80":81,"_85":33,"_86":87},"categories",[],"content_types",[44],"image","date_registered","2017-09-04T05:24:22.042303Z","description","","is_private","last_updated","2017-09-04T07:01:39.954638Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[56],"application/vnd.docker.container.image.v1+json","name","pull_count",793,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","# Azure Web Application for Containers - Developer Finder\n\nThe Developer Finder application is a container based application that demonstrates how to make a web application with multiple technologies and containers. \n\nThis sample includes a web application that allows users to authenticate and register with their GitHub and LinkedIn accounts, import data into their user profiles from those systems, and supplement their profile with additional information. The web application also provides users the ability to search for developers based on the information in their profile, and even suggests friends based on common profile information.\n\nIn addition to the profile and search capabilities, the web application interacts with a custom chat system that allows users to engage in chat conversation on the web site.\n\nThe entire application is packaged inside Docker containers and deployed to Microsoft Azure. In addition to the container apps, Azure resources such as a MySQL database, Application Insights, and other Azure services are used to implement the application.\n\n**Table of contents**\n\n* [Architecture](#architecture)\n * [Containers](#Containers)\n * [Web App](#web-app)\n * [Chat App](#chat-app)\n * [Azure Services](#azure-services)\n * [Databases](#databases)\n * [Application Insights](#application-insights)\n * [Geo-Replication](#geo-replication)\n* [Deployment](#deployment)\n * [Choose a name for the app](#choose-a-name-for-the-app)\n * [Register OAuth applications](#register-oauth-applications)\n * [GitHub Authorization](#github-authorization)\n * [[Optional] Register a Twilio account to send SMS](#optional-register-a-twilio-account-to-send-sms)\n * [Deploy the Azure Components](#deploy-the-azure-components)\n * [Configure TrackCustomEvent function URL](#configure-trackcustomevent-function-url)\n * [Set up the CI/CD](#set-up-the-cicd)\n * [Validate deployment](#validate-deployment)\n* [Demo scenario overview and flow](#demo-scenario-overview-and-flow)\n* [Running the demo](#running-the-demo)\n\n## Architecture \n\nThe following diagram illustrates the overall system architecture.\n\n![](Images/architecture.jpg)\n\nThe main components of the application are described in subsequent sections in this document.\n\n### Containers\n\n2 Docker images implement the system, each runs in its own container and they communicate via HTTP/HTTPS.\n\nThe following diagram illustrates the containers.\n\n![](Images/containers.jpg)\n\n### Web App\n\n#### Back-end \n\nThe back-end is a Python (3.6) App. \n\n* Uses the [Flask microframework](http://flask.pocoo.org/) to implement the web app and routing.\n\n* Uses the [Python Social Auth](https://python-social-auth.readthedocs.io/en/latest/) library to enable GitHub and LinkedIn accounts to login and returns user profile information from these systems. \n\n The following paths are exposed for authentication:\n\n | Path | Description |\n | ------------------------------------ | ---------------------------------------- |\n | /login/** | Navigates users to GitHub/LinkedIn login page |\n | /complete// | Endpoint that handles OAuth callback |\n | /logout | Logout current user |\n\n* Uses [Azure Database for MySQL](https://azure.microsoft.com/en-us/services/mysql/).\n\n* Uses [peewee](http://docs.peewee-orm.com/en/latest/) for ORM access to the MySQL Database.\n\n* Exposes the following APIs:\n\n | Action | Path | Description |\n | ------ | ----------------------- | ---------------------------------------- |\n | GET | /api/me | Get current user's profile |\n | POST | /api/me | Update current user's profile |\n | GET | /api/connected-accounts | Get current user's connected accounts |\n | GET | /api/friends | Get current user's friend |\n | POST | /api/friends | Add a friend for current user |\n | GET | /api/profiles | Get user profiles |\n | GET | /api/profiles/** | Get a profile by id |\n | GET | /api/profiles/suggested | Get suggested profiles (friends) for current user |\n | POST | /api/sms | Send a SMS |\n | GET | /api/messages | Get new messages sent to current user |\n | POST | /api/messages | Send a message from current user |\n | GET | /api/messages/summary | Get messages summary (unread count) |\n\n#### Font-end\n\nThe front-end is an AuglarJS App which provides the following pages:\n\n| Page | Path | Description |\n| ---------- | --------------- | ---------------------------------------- |\n| Login | /login | Allows users to login with GitHub or LinkedIn account |\n| Connect | /connect | Allows current user to connect to the other account |\n| My Profile | /profile | Allows current user to view and edit his/her profile |\n| Search | /search | Allows current user to search friends, add friend, and start a chat |\n| Profile | /profile/** | Allows current user to view other devs' profile |\n| Chat | /chat/** | Allows current user to chat with a dev or a friend |\n\n#### Nginx \n\nThe Nginx combines the back-end app and front-end app, and exposes them through the same port - 80.\n\nIt also works with [uwsgi](https://uwsgi-docs.readthedocs.io/en/latest/) to serve the back-end Python app.\n\n### Chat App\n\nThe Chat App is a very simple chat back-end application implemented with Ruby-on-Rails.\nIt does not include an authorization/authentication module, and has no user interface.\n\n* Built on [Ruby](https://www.ruby-lang.org/en/).\n* Uses a [PostgreSQL database](https://www.postgresql.org/). \n\nThe Ruby Chat app exposes the following APIs:\n\n| Action | Path | Description |\n| ------ | ---------------------------------------- | ------------------- |\n| POST | /api/messages | Send a new message |\n| GET | /api/messages/summary?to=** | Get message summary |\n| GET | /api/messages/unread?from=**&to=** | Get unread messages |\n\n### Azure Services\n\nAzure Services are also used to implement the application. The following services are used.\n\n1. Function App\n * Logs custom metrics to Application Insights.\n2. Logic App\n * Sends SMS text messages to users.\n\n### Databases\n\n#### MySQL Database\n\nThe MySQL Database is used by the Web App. It contains the following tables.\n\n| Table | Description |\n| -------------- | ---------------------------------------- |\n| user | Stores user info, like username and email |\n| usersocialauth | Stores users' connected social account info, like provider and uid
It contains a foreign key column user_id referencing the primary key column of the user table |\n| profile | Stores users' profiles |\n| position | Stores users' positions
It contains a foreign key column profile_id referencing the primary key column of the profile table. |\n| friend | Stores friends relationship
Its 2 columns, user_id and friend_id, are foreign keys referencing the primary key column of the user table |\n\n>**Note:** In a true production environment, the data in the usersocialauth table would most likely be stored in a separate database to make the solution more secure. In this sample, it is stored in the same database to simplify the solution and the deployment process.\n\nThe **profile** table contains several columns which are divided into 5 groups:\n\n* Primary key:\n * id: matches the id column value in the user table\n* Values managed by My Profile page:\n * phone_number: user’s phone number\n * skills: comma separated string, for example: *c#, Python, Ruby*\n* Values retrieved from GitHub and LinkedIn accounts:\n * company: user’s current company\n * location: user's location\n * name: user display name\n* Values are retrieved from GitHub only:\n * github_profile_url: the URL to user’s GitHub profile page\n * blog_url: the URL to user's blog\n * hireable: boolean indicating if the user is hireable\n * bio: user's biography\n * public_repos: the number of public repos\n * public_gists: the number of public gists\n * followers: the number of followers\n * following: the number of users the user is following\n * avatar_url: the URL to the user’s avatar\n* Values are retrieved from LinkedIn only:\n * industry: The industry the member belongs to\n * num_connections: the number of LinkedIn connections the member has, capped at 500. See 'num-connections-capped' to determine if the value returned has been capped.\n * num_connections_capped: returns 'true' if the member's 'num-connections' value has been capped at 500', or 'false' if 'num-connections' represents the user's true value\n * linkedin_standard_profile_url: the URL to the member's authenticated profile on LinkedIn. You must be logged into LinkedIn to view this URL.\n * linkedin_public_profile_url: the URL to the member's public profile on LinkedIn\n\n#### PostgreSQL Database\n\nThe PostgreSQL database is used by the Chat App. It is very simple and only contains 2 tables:\n\n| Table | Description |\n| -------------------- | ----------------------------------- |\n| messages | Stores all the messages |\n| message_read_records | Records users' last read message id |\n\n### Application Insights\n\nThroughout the application, custom events are logged to Application Insights.\n\nThe following table describes the custom events logged to Application Insights at a high level.\n\n| Source | Triggers |\n| --------------- | ---------------------------------------- |\n| Python Web App | Python REST API, Function, and Logic App Calls |\n| Python REST API | Python REST API, Function, and Logic App Calls |\n| Logic App | Start, Events Taking Place In Logic App, Complete |\n\nThis image shows custom events logged to Application Insights.\n\n![](Images/application-insights-1.jpg)\n\nThe following image shows the detail of a custom event. In this example, the /api/messages/summary Python REST API was successfully invoked.\n\n![](Images/application-insights-2.jpg)\n\n### Geo-Replication\n\nBecause this is a sample application that is designed for anyone in the world to deploy their own isolated instance, the databases in the application are created each time the ARM template deploys the solution. The web apps are tied directly to the databases that are deployed.\n\nSince this is the case, if you Geo-Replicate the solution, each Geo-Location will have a separate copy of the databases. You are still able to demonstrate Geo-Replicating the app as part of the demo, but if you Geo-Replicate the solution then subsequently logged into an instance of the app in the US with one user, and logged into an instance of the App in China with another user, they would not be able to see each other in search results or chat because they are interacting with separate databases.\n\nIn a real production scenario, there would be a common database, or multiple databases with a database sync. This would provide the ability to use the Traffic Manager to load balance traffic across multiple Geo-Locations and achieve global scale with the solution. You can re-architect the solution to provide these capabilities.\n\n## Deployment\n\n### Choose a name for the app\n\nThe name of the application is 'Developer Finder'. We suggest you follow the naming convention below when creating your instance of the application:\n\n\t**developer-finder-[suffix]**\n\nThe suffix is used to avoid Azure resource naming conflicts. \n\n> **IMPORTANT NOTE: Only use lowercase letters (a-z), numbers (0-9), and hyphens (-). Uppercase letters will cause errors to occur.**\n\nBelow are some examples:\n\n* developer-finder-contoso (company name is used)\n* developer-finder-0901-1200 (date and time are used)\n\nIn this document, we use the first example to show you how to deploy the solution to Azure. When you are finished with the deployment, you will be able to browse to the web application by navigating to this URL in a web browser:\n\n\thttps://developer-finder-[suffix].azurewebsites.net\n\n\tExample that matches the example in this document: \n\n\thttps://developer-finder-contoso.azurewebsites.net\n\n### Register OAuth applications\n\nTo start, you must register OAuth applications for GitHub and LinkedIn. These OAuth applications allow the application to authenticate to GitHub and LinkedIn and download user profile information stored in these systems.\n\n#### Register GitHub OAuth application\n\n1. Sign into GitHub.\n2. Open https://github.com/settings/applications/new\n3. Fill the form with the following information:\n\n * Application name: **Developer Finder**\n\n * Homepage URL: **https://developer-finder-[suffix].azurewebsites.net**\n\n > **Note:** Replace the **[suffix]** placeholder with the one you choose to use. Use this same value throughout the deployment process.\n >\n > **Example:**\n >\n > \thttps://developer-finder-contoso.azurewebsites.net\n\n * Authorization callback URL:\n\n **https://developer-finder-[suffix].azurewebsites.net/complete/github/**\n\n > **Note:** Replace the **[suffix]** placeholder with the one you choose to use. Use this same value throughout the deployment process.\n >\n > **Example:**\n >\n > \thttps://developer-finder-contoso.azurewebsites.net/complete/github/\n\n4. Click **Register application**.\n5. Copy aside the **ClientID** and **Client Secret**.\n\n > **Note:** These values will be used for the **OAuth GitHub Client Id** and **OAuth GitHub client Secret** ARM template parameters.\n\n#### Register LinkedIn OAuth application\n\n1. Sign into LinkedIn.\n\n2. Open https://www.linkedin.com/developer/apps/new\n\n3. Fill the form with the following information:\n\n * Name: **Developer Finder**\n\n * Application Logo: download and use the image below\n\n ![](Images/developer-finder.png)\n\n * Website URL: **https://developer-finder-[suffix].azurewebsites.net**\n > **Note:** Replace the **[suffix]** placeholder with the one you choose to use. Use this same value throughout the deployment process.\n >\n > **Example:** \n >\n > ```\n > https://developer-finder-contoso.azurewebsites.net\n > ```\n\n4. Input the other required fields, then click **Submit**.\n\n5. Add the OAuth 2 Authorized Redirect URL: \n\n **https://developer-finder-[suffix].azurewebsites.net/complete/linkedin-oauth2/**\n\n > **Note:** Replace the **[suffix]** placeholder with the one you choose to use. Use this same value throughout the deployment process.\n >\n > **Example:**\n >\n > \thttps://developer-finder-contoso.azurewebsites.net/complete/linkedin-oauth2/\n\n6. Click **Update**.\n\n7. Copy aside the **ClientID** and **Client Secret**.\n\n > **Note:** These values will be used for the **OAuth LinkedIn Client Id** and **OAuth LinkedIn Client Secret** ARM template parameters.\n\n### GitHub Authorization\n\n1. Generate Token:\n\n - Open https://github.com/settings/tokens in your web browser.\n\n - Sign into GitHub.\n\n - Fork this repository to your GitHub account.\n\n - Click **Generate Token**.\n\n - Enter a value in the **Token description** text box.\n\n - Select the following scopes (your selections should match the screenshot below):\n\n - repo -> repo:status, repo_deployment, public_repo\n\n - user -> read:user, user:emial, user:follow\n\n > Note: the user scope itself must be selected.\n\n ![](Images/github-new-personal-access-token.png)\n\n2. Add the GitHub Token to Azure in the Azure Resource Explorer:\n\n * Open https://resources.azure.com/providers/Microsoft.Web/sourcecontrols/GitHub in your web browser\n\n * Log in with your Azure account\n\n * Selected the correct Azure subscription\n\n * Select **Read/Write** mode\n\n * Click **Edit**\n\n * Paste the token into the **token parameter**\n\n ![](Images/update-github-token-in-azure-resource-explorer.png)\n\n * Click **PUT**\n\n### [OPTIONAL STEP] Register a Twilio account to send SMS \n\nWhen a chat is started between two users in the application, the app will send an SMS to notify the user the message was sent to them. \n\nThis app uses a Twilio trial account to send SMS.\n\nIf you wish to enable the SMS capabilities in the application you must create a Twilio trial account and register and verify a phone number to send SMS.\n\n#### Create and configure a Twilio trial account\n\n1. Register a trial account\n\n * Open https://www.twilio.com/, then click **Get a free API key**. \n * You will be redirected to **Sign up for free page**. Fill in the form, then click **Get Started**.\n * Twilio will show a page verify you're a human. Finish it.\n\n2. Create a project\n\n After the human verification is complete, you will be redirected to a page to let you create a project.\n\n * Input a name, for example: **Developer Finder**, then click **Create Project**.\n\n * After the project is created, copy aside the **ACCOUNT ID** and **AUTH TOKEN** values.![](Images/twilio-api-credentials.png)\n\n > **Note:** These 2 values will be used for the **Twilio Account SID** and **Twilio Auth Token** ARM template parameters.\n\n3. Get a phone number:\n\n * In the **Phone Numbers** section, click **Manage Numbers**.\n * Twilio will redirect you to the **Phone Numbers Dashboard**.\n * Click **Get Started**.\n * Click **Get you first Twilio phone number**.\n\n > **Note:** Twilio will pre-select a phone number. Use the number it gives you.\n * Click **Choose this number**:\n\n ![](Images/twilio-phone-number.png)\n\n * Copy aside the phone number.\n\n > **Note:** This phone number will be used for the **Twilio From Phone Number** ARM template parameter.\n\n#### Verify a phone number\n\n1. Click **Verified Caller IDs** on the **Phone Numbers page**:\n\n ![](Images/twilio-verified-caller-ids.png)\n\n2. Click the red **⊕**:\n\n ![](Images/twilio-verify-a-phone-number.png)\n\n3. Follow the instructions to verify the phone number.\n\n### Deploy the Azure Components\n\n1. In your web browser, navigate to your fork of this repository.\n\n2. Click the **Deploy to Azure** button below:\n\n [![Deploy to Azure](http://azuredeploy.net/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure-App-Service%2FDemoApp%2Fmaster%2Fazuredeploy.json)\n\n3. Fill in the values in the deployment page:\n\n ![](Images/azure-deploy-basic.png)\n\n * Resource group: \n\n We suggest you create a new resource group and name it **DeveloperFinderRG**.\n\n * Location: \n\n Web Apps on Linux are currently (2017/08) only available in the following regions. So, you must choose one of the regions below:\n\n * West US\n * East US\n * West Europe\n * North Europe\n * South Central US\n * North Central US\n * Southeast Asia\n * East Asia\n * Australia East\n * Japan East\n * Brazil South\n * South India\n\n ![](Images/azure-deploy-settings.png)\n\n * Web App Name: \n\n Use the name you chose at the start of these instructions that follows the **developer-finder-[suffix]** naming convention.\n\n * No-Linux Web App Location: \n\n You **MUST choose a different region for the non-Linux web apps**, because they cannot be created in the same region and the same resource group.\n\n * OAuth Git Hub Client Id & Secret: \n\n Use the client id and secret of the GitHub OAuth app.\n\n * OAuth LinkedIn Client Id & Secret: \n\n Use the client id and secret of the LinkedIn OAuth app.\n\n * Database Admin Login Name: \n\n It cannot be 'azure_superuser', 'admin', 'administrator', 'root', 'guest' or 'public'.\n\n * Database Admin Login Password: \n\n This field should be between 8 and 128 characters long. Your password must contain characters from three of the following categories – English uppercase letters, English lowercase letters, numbers (0-9), and non-alphanumeric characters (!, $, #, %, etc.).\n\n * Ruby Chat Docker Image:\n\n Please keep the default value: *appsvc/demoapp-rubychat*.\n\n\n * Twilio Account SID & Auth Token & From Phone Number.\n\n Use the values you got from you Twilio account.\n\n * Source Code Repository URL:\n\n Use the URL of the repository you just cloned.\n\n4. Check **I agree to the terms and conditions stated above**.\n\n5. Click **Purchase**.\n\n6. Wait until the ARM template deployment process completes.\n\n### Configure TrackCustomEvent function URL\n\n1. Get TrackCustomEvent function URL from the Function App.\n\n - Open the Function App in the Resource Group:\n\n ![](Images/function-app.png)\n\n - Expand the functions, then click **TrackCustomEvent**. Click **Get function URL** at the right.\n\n ![](Images/function-app-url.png)\n\n - Copy the URL on the popup.\n\n2. Configure application settings of the Web App.\n\n - Open the Web App in the Resource Group:\n\n ![](Images/web-app.png)\n\n - Click **Application settings**\n\n ![](Images/web-app-settings.png)\n\n - Find the *TRACK_CUSTOM_EVENT_FUNCTION_URL* setting, paste the function URL you just copied to its value inputbox.\n\n - Click **Save**.\n\n### Set up CI/CD\n\n1. Navigate to the resource group you just created and deployed, then click the **developer-finder-[suffix]** Web App:\n\n ![](Images/web-app.png)\n\n2. Click **Continuous Delivery**, then click **Configure**:\n\n ![](Images/web-app-cd.png)\n\n3. Click **Choose container registry**, the pre-configured private registry will be loaded:\n\n ![](Images/configure-cd-01.png)\n\n4. Click **OK** (the right one).\n\n5. Click **Configure continuous delivery**:\n\n ![](Images/configure-cd-02.png)\n\n * Code repository: choose **GitHub**.\n * Repository: choose this GitHub repository that you forked.\n * Branch: choose **master**.\n * Dockerfile path: change it to **Dockerfile**.\n\n6. Click **OK** (the right one).\n\n7. Click **Select a Team Service account**:\n\n ![](Images/configure-cd-03.png)\n\n * Create a new account or using an existing one.\n * Create a new project or using an existing one.\n8. Click **OK** (the right one).\n\n9. Click **OK**.\n\n > **Note:** It takes a few minutes to finish:\n >\n > ![](Images/configure-cd-done.png)\n\n### Validate deployment\n\nOpen the http**s**://**developer-finder-[suffix]**.azurewebsites.net web app.\n\n> **Note:** \n>\n> 1. Make sure you use http**s** instead of http.\n>\n> 2. Make sure you replace the [suffix] placeholder with the value you have used throughout the deployment process.\n>\n> **Example:** https://developer-finder-contoso.azurewebsites.net\n\nYou will see the login page:\n\n![](Images/web-app-login.png)\n\n> **Note:** If you get a \"502 Bad Gateway\" error, please wait for a few minutes and try again. \n\n## Demo scenario overview and flow\n\nSee the [Demo Script](Demo%20Script.pptx) slide deck.\n\n## Running the demo\n\nFollow the steps in [Demo Script](Demo%20Script.pptx) slide deck.\n\n## Contributors ##\n| Roles | Author(s) |\n| -------------------------- | ---------------------------------------- |\n| Project Lead / Architect | Todd Baginski (Microsoft MVP, Canviz) @tbag |\n| Architect / Developer Lead | Tyler Lu (Canviz) @TylerLu |\n| Developer | Albert Xie (Canviz) |\n| Developer | Hubert Sui (Canviz) |\n| Design | Justin So (Canviz) |\n| Testing | Cindy Yan (Canviz) |\n| Sponsor / Support | Ahmed Elnaby (Microsoft) |\n| Sponsor / Support | Stella Lin (Microsoft) |\n\n## Version history ##\n\n| Version | Date | Comments |\n| ------- | --------------- | --------------- |\n| 1.0 | August 31, 2017 | Initial release |\n\n## Disclaimer ##\n**THIS CODE IS PROVIDED *AS IS* WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR NON-INFRINGEMENT.**\n","has_starred","hub_user","immutable_tags_settings",{"_75":11,"_76":77},"enabled","rules",[78],".*","is_automated","permissions",{"_82":21,"_83":11,"_84":11},"read","write","admin","user","storage_size",396030145,"orgData","recentTags",[91],{"_92":44,"_93":94,"_95":96,"_97":98,"_99":100,"_50":117,"_118":94,"_119":33,"_120":56,"_57":121,"_122":123,"_124":108,"_125":117,"_126":66,"_127":21},"content_type","creator",1587192,"full_size",367335098,"id",14831870,"images",[101],{"_102":103,"_104":105,"_106":48,"_107":108,"_109":110,"_111":112,"_113":48,"_114":-5,"_115":96,"_63":66,"_116":-5},"architecture","amd64","digest","sha256:0d7a9c47ff7c23205065aff8f76319b326f636b5d707e244bffe43a3713409d5","features","last_pulled","2026-09-28T01:02:02.517977245Z","last_pushed","2017-09-04T07:01:40Z","os","linux","os_features","os_version","size","variant","2017-09-04T07:01:39.636364Z","last_updater","last_updater_username","media_type","latest","repository",1789775,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"selectedTag","attestationsUrl","routes/_layout.r.$namespace.$reponame.tags",{"_38":141,"_148":149,"_135":158,"_159":11},{"_40":142,"_42":143,"_45":46,"_47":48,"_49":11,"_50":51,"_52":53,"_54":144,"_57":35,"_32":33,"_58":59,"_60":44,"_61":62,"_63":64,"_65":66,"_67":-5,"_68":62,"_69":70,"_71":11,"_72":33,"_73":145,"_79":11,"_80":147,"_85":33,"_86":87},[],[44],[56],{"_75":11,"_76":146},[78],{"_82":21,"_83":11,"_84":11},"tags",{"_150":64,"_151":-5,"_152":-5,"_153":154},"count","next","previous","results",[155],{"_92":44,"_93":94,"_95":96,"_97":98,"_99":156,"_50":117,"_118":94,"_119":33,"_120":56,"_57":121,"_122":123,"_124":108,"_125":117,"_126":66,"_127":21},[157],{"_102":103,"_104":105,"_106":48,"_107":108,"_109":110,"_111":112,"_113":48,"_114":-5,"_115":96,"_63":66,"_116":-5},[],"canDeleteTags","actionData","errors"]

tylerlu/demoapp-base

Tags for tylerlu/demoapp-base