Ape Fist posted:

Interacting with Docker for the first time is as unpleasant or perhaps more unpleasant than interacting with Git.

Ape Fist posted:

Interacting with Docker for the first time is as unpleasant or perhaps more unpleasant than interacting with Git.

The Fool posted:

If I gently caress up with git I risk my entire commit history.

Thermopyle posted:

Docker, like git, is pretty easy for the 90 percent use case if you take the time to read the docs thoroughly instead of just Googlin for the one thing you think you need to do.

Roadie posted:

Vincent Valentine posted:

Genuinely curious: Are you going to provide a Few Updates™?

Awesome Animals posted:

Now that I use it regularly and switch between different micro services the company I work for maintains, all with different versions of rails, ruby, and Postgres, I find it absolutely critical.

Roadie posted:

I've always felt like the software world being ridiculously terrible at versioning compatibility like this is 95% of why Docker exists.

Vincent Valentine posted:

Yeah that's been my experience. If you want someone's username and password, just ask. They'll tell you.

PT6A posted:

If they don't, suggest that they have to move five feet and spend 30 seconds typing in a username and password. They'll be so frightened of work they'll write them down for you!

The number of passwords I know from not-even-intentional social engineering is immense.

Vintersorg posted:

code:

:min-date="new Date(Date.now()-604800000)"

Date calculated using milliseconds.

Lumpy posted:

/me eagerly awaits daylight savings time derail

The Fool posted:

Just use a library like moment

Ape Fist posted:

That's not going to solve all your problems trust me.

prom candy posted:

ban all time zones

uncle blog posted:

Hi guys. Our React app loads some data from a graph db. We are currently using Apollo for this, and I'm a bit unsure of best practices and how this service is supposed to work with states.

We load a list of different "goals" a user can choose from. This is done in the App.tsx component, which contains routes all the other pages. We also have a state object for which "goal" the user has chosen. We initially loaded all the goals from a static json, and would initialize the chosen goal state object from this json list. But now we need to set this as one of the loaded goals, when useQuery has finished loading the data. So I figured I would use useEffect for this. But this isn't working properly and feels wrong, like I'm missing something about how Apollo should be used?

code:

const App = () => {
  const {
    loading: goalListLoading,
    error: goalListError,
    data: goalListData
  } = useQuery(GOAL_LIST_QUERY, {});

 const [userGoal, setGoal] = useState({ id: "", Description: "", Name: "" });

 useEffect(() => {
    if (goalListData && goalListData.contexts) {
      setGoal(goalListData.contexts[0]);
    }
  }, [goalListData]);

Also, to handle errors on the page where the goals can be selected, I wanted to pass in the error object from useQuery as a prop. But again, this feels like I'm working against the conventions of Apollo and that I'm doing a bunch of hacky poo poo?

code:

<Route
          exact
          path="/goal"
          render={props => (
            <GoalPage
              prevPath="role"
              nextPath="obstacle"
              isError={goalListError ? true : false}
              onGoalChange={handleGoalChange}
              {...props}
            />
          )}
        />

Thermopyle posted:

You should never use the system python unless it's a system script.

Always use virtual environments.

Every language has the same leaky abstractions problem.

Python has a bad packaging/dependencies story.

Vitual envs are an ok solution to that.

Lumpy posted:

Seems to me the query and state are one level up from where they should be. GoalPage should care about that stuff, not App. If for some reason the whole app does care about that, you could use Context to make common state shared, or keep it in @client in the Apollo store and have queries inside components that care about it (or just have them duplicate the apps useQuery if it is cached)