A user interface for AWS for writers

Abierto
#153 1 comentario 1 reacción 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
15/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
aws
Área
cloud

Línea de trabajo

The issue names no repository files, tests, or entry points. Start by defining the AWS authorization flow for non-developers and the creation of private and public S3 buckets for Little Outliner. Done should include a documented, workable account-authorization and bucket-access flow, but the issue does not specify implementation or test criteria.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Here's an interesting piece of data.

I said Hey Doc, create an AWS account. I didn't tell him how to do it. I wanted to see what happened. He didn't succeed.

OK so this means to me that we need a piece of software. A rough idea of how it would work. The user signs on to their Amazon account, the one they use to buy socks, and then authorizes you to act on its behalf with AWS. Ideally that would feel, to the user, like giving access to an app to use their Twitter identity. From there, you create a pair of S3 buckets, one private and one public. Then you allow my software, Little Outliner, to access his bucket.

I don't know what all these steps are. But it should draw on a user's ability to create accounts on other popular services. I imagine it's what Amazon itself would create if they wanted to provide a service to non-developers. I imagine at this time they consider it a "developer opportunity."

I need this functionality as a go-between my users and my software. I don't want to store their stuff long-term, because I don't have a long-term. :-)

Lenguaje dominante
HTML
Estrellas
134
Forks
10
Sin PR fusionados en 30 d

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de scripting/Scripting-News

Todos los issues de scripting/Scripting-News

Issues similares

Más issues de Cloud

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.